Adobe Workfront General

Description - After a thorough implementation, we decided to use the Request Queues built directly in the projects. The functionality is great. We have a project template set up with Queue Topics, Groups, Forms etc. The issue is that when creating requests directly in a project there is no Autosave or Drafting functionality that we know of. Our users are becoming increasingly agitated by having complex requests easily deleted at the unfortunate click out of the request window or accidental refresh of the page.   Why is this feature SO VERY important to you - Our current solution is to submit requests without auto-routing to a traffic team so the work can be saved. Leading to needing to save as you go, something that is antiquated in this day and age, especially knowing that autosave exists in many other places in Workfront, including the Global Request Queues area.   How would you like the feature to work - simply autosave as you go with a Drafts section built into the Reque

Tracking approver decision counts across proofs (in Workfront AND in ProofHQ/Proofing Tool) to manage the 6-decision/month threshold before contributors shift to light access — that’s a genuine reporting gap.Currently, there is no visibility into Proofs that were generated in Workfront Poof Tool. We need to be able to report from Workfront on the user level to track/count decisions that will count towards a user’s decision threshold before they are automatically moved from a contributor to a light user.

In the past update notifications included the author as the from name in email notifications. Now the sender is simply Workfront. This makes it easy to overlook and difficult to identify/distinguish emails. Please reinstate the prior behavior with the updated format. 

Integration with Microsoft Word and Workfront. We would like to have tracked changes inside of WF or to have the ability to edit documents within the proofing tool.

We used to be able to right-click on the sidebar area to the left of the project info. 'Tasks, Documents, Project Details, etc.' could be right-clicked and have opened in a new tab/window. A few montsh ago the UI team changed that option and right-clicking those is no longer available. I’m hoping there's a way to bring that back as it was REALLY helpful when trying to see two different sections of the project quickly.  The removal of the right-click functionality on the project left panel navigation items is a product design change that was made as part of a platform update. I’d love for it to be brought back as an easier part of the Workfront workflows. 

We’re going through a taxonomy/metadata exercise to map our organization’s taxonomy across our enterprise with Workfront and AEM.While this page is available:  https://developer.adobe.com/workfront/api-explorer/You can’t export the fields or the data.This would be nice to have when mapping and integrating.

My organization uses Workfront Planning to manage our Enterprise Strategic Plan. Initially, users submit very early stage Strategic Plan Requests for initial review. If it is determined by leadership that it aligns with the organization's strategic goals, they are approved to begin discovery. The Request itself is not approved at this time, it is just moved to a different status, indicating they can move forward with discovery. Once discovery is complete, it is reviewed again, and only then if approved does it move over to Workfront Proper to become a full project.This discovery could take years in some cases, and is occurring while the item is still a Request in Planning. We need a way for these users to track their time contributed to the discovery process.

My organization uses Workfront Planning to manage our Enterprise Strategic Plan. Through the use of structured taxonomies, we’re able to create a timeline view that allows for the breakdown Strategic Theme -> Strategic Sub-Theme -> Strategic Statements -> Projects, showing where each project falls on the timeline that impacts its associated strategy.We'd like to break it down a step further and be able to expand each Project associated with a Strategic Statement within that timeline view to show the Milestones within the Project, or specifically labeled Parent Tasks, allowing teams to view where each phase of any given Initiative then falls within the overall project timeline all in one view.Currently we're unable to do so as the only available Workfront Object Types to connect to in Planning are Project, Portfolio, Program, Company, Group and Original Request.

Hello! We would like to propose that when using a Workflow Template for Proofing that the V2 (Version 2) of that document would follow the deadline days and time as formatted in the initial template set up. Thank you!

It is a huge inefficiency that we cannot bulk edit like items on template tasks in multiple templates. For example, I want to bulk edit a value on the same task custom form in multiple template tasks/across multiple templates. I pull all of the tasks in a template task report, select the several I want to change, all of which have the same task custom form, and you cannot do this. You get the error below. You can bulk edit tasks across projects, why can we not bulk edit tasks across multiple templates?  

When creating a report, you have the Report Default view that is naturally created which works great for a lot of specific reports, but we find creating reporting for multiple teams challenging as they want to see different data elements (different columns) based on their role; looking for options to avoid creating multiple reports for basically the same thing and also increase the ease of using reports without having to team users which views go with which reports and also which ones simply are used potentially in project list views or somewhere else.  Idea:   Have the ability to create or associate specific views (columns/formatting) and tag them to a report.  Ideally, this would be available in a section on top with predefined reporting views that users can quickly navigate between.    Bonus:   Have the option to select a view based off simple rules such as If TeamID = Leader then present the Leadership view (configured when creating the report!)  

It’s not ideal to have to type “confirm” each time you want to update a field value. For some fields we have 20+ values that need to be updated. It would be better to unlock all of the values for a field after confirming once.Also, the process of confirming itself is not intuitive. It’s not obvious that you need to type “confirm” instead of the updated value itself. It would be better to have a “Confirm” button.

I find where I spend most of my time utilizing the log in as feature is on testing new reports - specifically ones where $$USER.ID is involved.I think it would be super helpful if there was a button for admins on the Report Actions to have a “View Report As” feature that allows admin’s to preview a report as a specific user to save all of the clicks between setup and reports. 

Users have high-priority need to take a Request that has been converted to a Project (using a specific template) and create a second project (with a different template) out of the original Issue/Request. Users would be able to browse from Request list and see all projects created from original request.

Description - The current functionality for routing rules is very limited. We are only able to configure routing rules for specific queue topics. Allowing us to assign specific user/teams to a specific queue topic.  The following is functionality that is possible through Fusion, but want to be available without Fusion: 1. Automatically Convert Requests/Issue into a Project If a request is submitted through a specific queue topic, then automatically convert the request into a project using a specific project template. Ideally, we would also have the ability to configure this at the custom form level. e.g. If the requester selects XYZ on the request form, then convert into a project using XYZ template. If the requester selects ABC on the request form, then convert into a project using ABC template.  2. Dynamic Request Routing Based on how the Form was CompletedSimilar to #1, allow us to set routing rules based on how the request form was completed. If c

To reduce the risk of accidental interruptions, we recommend moving the Schedule Sandbox Refresh button from the main Workfront page to the Setup menu.Keeping this action button on the main page makes it easy for users who are not involved in the refresh process to unintentionally cancel or modify a scheduled refresh, which could directly impact planned activities.Since refreshes are typically coordinated internally by the team before execution, placing this option under the Setup menu provides an additional layer of protection, ensuring that only authorized users performing configuration tasks can access it and significantly reducing the likelihood of accidental changes.

I would like there to be a global Workload Balancer setting that automatically hides ON HOLD or DEAD projects without applying status-based filter criteria or needing to update the project tasks so they don’t qualify. Similar to the how completed work can be removed from the Workload Balancer through the Show completed work setting, it would be ideal if there was a Show Dead or On Hold work setting that could be toggled off once in settings rather than having to add criteria [Project: Status -- Does not equal -- Dead, On Hold] to all Workload Balancer active project filters to exclude these projects. USE CASE: When an in-flight project is cancelled or put on hold, setting its status to DEAD or ON HOLD allows the Project Owner to freeze the project where it was in its progress without having to complete or clear the qualifying tasks to remove them from showing in the Workload Balancer. That way if the project happens to come back to life down the line, the remaining tasks are still set

Problem StatementIn Workfront, users submit requests through the system and may need to coordinate with colleagues in other departments on the same request. Today, if a user wants another person to be engaged in the request conversation, the most common process is to wait until after the request is created and then manually add an @ mention in the Updates section.This creates friction and can lead to communication occurring outside the request context—especially when users choose an easier workaround.Current WorkaroundAfter creating the request, users go to the Updates area and @ tag the relevant person.However, many users find it easier to:open the email notification they received for the request, and forward that email to the teammate in the other department.As a result, communication is no longer centralized in Workfront, and the “single source of truth” for the request is reduced.Proposed EnhancementCreate a field type (or input capability) that allows users to @ tag/mention others

Description—It would be ideal if we could Upload and Host an Image to be used in our Custom Forms. Currently, we only have the option to add images by adding the URL of an image hosted somewhere else. The images/documents inside Workfront do not work, as they expire after a few minutes. Why is this feature important to you - This would make the feature easier to use, and located all in one place (Workfront) How would you like the feature to work? If I choose to add an Image in the Custom Form, it would be helpful if I had the option to Upload a File to be used. That file will stay in Workfront and be connected to that Custom Form. Any User with access to the Custom form would also have access to the file. Current Behaviour—Currently, there is no option to upload an Image. We can only enter a URL. Images and documents hosted in Workfront can be added as part of the URL, but because those URLs expire after a few minutes, they generate an Error or broken link and a bad expe

Adding an Employee ID field to the user profile would be a valuable enhancement for organizations that rely on unique employee identifiers across multiple systems.In our environment, duplicate names are fairly common, making it difficult to distinguish between users. An Employee ID field would provide a reliable way to identify the correct person and improve data accuracy.This would be especially helpful in Fusion integrations that map Workfront user information to Salesforce, where we often need a unique identifier rather than a user name.It would also be great if the Employee ID field could be added as a selectable column in user views and reports, enabling administrators to easily reference and validate user records.I hope that you will consider this enhancement request.

It would be helpful to have the option to display the updates in order by the last update made. When reply is added to an older update, it is difficult to search for because the original post is displayed way down the update feed. When a reply is made to an older comment, it would be nice to have it move to the top, truly in order of last update, be it original or a response.

The new green pop-ups at the bottom of the screen when task status is modified, such as if you click work on it the pop-up says “You’ve started working on this. The status is now in progress.” or when you remove your assignment it says “You’ve stopped working on this, the status is now new” are persistent and must be manually dismissed by users even after navigating to other objects. While having the pop-up is helpful for confirmation, we need the ability to have those auto-dismiss after a few seconds or at least have it disappear when moving to a different object in Workfront.We have users who are moving quickly through the system who now feel disrupted by having to click another item to dismiss after already clicking to change the task. They often move on quickly until these pile up at the bottom of their screen, then have to dismiss each individually. Which a large volume of work as is, any extra clicks are cumbersome to users. Thank you so much! 

I recently started receiving incessant in-app notifications when a team to which I'm assigned receives a work request. They look like this: [Person] wants your team, [Team], to work on this task. Many members of our department are assigned to multiple teams, causing each of us to receive dozens of notifications per day--even per hour--for new assignments that rarely apply to us. I'm told there's no way to opt out of these in-app notifications. Please add a way to opt out of certain notification types--or at least turn these off again (as they have been since we started using Workfront a year and a half ago).

Just like we can delegate project/task/issue approvals, and with 22.3 can delegate task/issue assignments, PLEASE have the ability to delegate proof approvals! There are other ideas for this with 'Not Planned' labeled, hoping power in numbers can help sway this bc this is something WF really needs. Hoping it is part of near-future proof enhancements.

Description: We would love to see additional fields directly visible on a card when looking at a board rather than clicking into each card.  Why is this feature important to you: This could help with quicker prioritization, understanding capacity, and organizing the work within a board without as many clicks/steps.  How would you like the feature to work: Unlock the Visible on Board option for custom fields for at least a few (understanding only so much fits on a card) like maybe having a space below the assignments/due date/status that allows for up to 2 or 3.  Current Behaviour: Visiblity on card only functional for pre-built fields   Thank you!