Adobe Workfront

Our team has a need to make the filter selection in the My Approvals widget sticky. We have multiple team members that submit work to others for approval and receive work from others for approval. Having to reset the filter each time to show only “My Approvals” instead of “All” wastes a few clicks of time and makes it more difficult for us to work through time-sensitive approvals. 

When users select the Search icon, it is natural to expect all relevant results to be visible on the first page. Currently, when our users are “searching” in Programs, the results are either not showing on the first page, or one is showing on the first page with the remainder displaying on different tabs/pages.WF Support has said that currently, this is due to the existing pagination behavior and is a product limitation. Unfortunately, this is causing confusion among our users.Thank you for your consideration.

At present it is not possible to disable the 'Select All' function for checkbox fields. It would be very useful to be able to deselect/disable this functionality for each checkbox field in the Admin layer of the form builder.

A checkbox for "ALL" appears by default on custom forms when using the checkbox feature. It happens after a certain number of choices are listed. We don't want our clients to be able to click ALL as it will prevent the client from really thinking through what they need. We don't want our clients to be able to click ALL just because it's faster.

This article makes the case for setting up a lightweight Workfront release management process, and shows how it's easier to implement than most people assume.Key points:The problem: Untested changes going live in Workfront can catch teams off guard and erode trust. The fix doesn't need to be heavy: Release management just means having a repeatable way to plan, test, approve, and communicate changes — not a bureaucratic approval chain. Two sandboxes, two jobs: SB02 (Sandbox 2) is where technical building and testing happens; SB01 (Sandbox 1) is where real users validate changes before go-live. Keep sandboxes fresh: Regular refreshes (SB02 more often, SB01 before major testing cycles) keep testing environments realistic — stale sandboxes give false confidence. Environment Promotion moves things along: Workfront's built-in packaging tool lets you move configuration changes (forms, fields, templates) between environments reliably, instead of manually rebuilding them each time — build → com

We would like the ability to limit users from being able to delete a task assigned to them. We don’t log hours we we are unable to remove that ability from them in the Project Preferences. The issue is when we try to remove the delete functionality from them, it also removes the ability for them to complete the work on the task. We tried going a layout template route as well suggested by support. According to support, Layout Templates only control the Delete action in the task Details view; there isn't a way to hide that same action in the project's task list (grid) view, since that's tied directly to the Delete permission on the Access Level. Because unchecking Delete at the Access Level can also block completing multi-assignee tasks, there isn't a configuration that fully satisfies both goals (deletion blocked everywhere, completion always working) at the same time today. 

Would love to have a button in WF that takes me to a text mode cheat code library vs. searching community or using AI. Any Workfront user could submit a cheat code and it gets added to a database behind the scenes. This would help all users be able to have quick access to effective text mode that works. This would speed up being able to implement solutions for reporting for businesses.

Currently, the only time the pre-defined sorts in a view (ie: sorts specified and saved in a view) are utilized is in a report (ie: View = Report Default). a) If you change the view on the report - from Report Default to another view - and the newly selected view has its own sorts defined, the report uses the sorts from the Report Default view; the report does not use the sorts defined in the selected view. b) Pre-defined sorts in views are not utilized when using views in a project. All of the above was confirmed by Workfront Support. Would like the system to use the sorts defined in the selected view, both in reports and in the project. Thanks

Currently the Percent Complete roll up at the Program level only takes into account Projects that are in "Current" status. This does not make much sense as you are completely ignoring all projects that have been fully completed and marked as such. If all projects under a program have been marked as complete status, then the Percent Complete at the Program level should show 100%

I am very frustrated by the lack of sharing ability with the Approval Workflows. why is the functionality limited to either a specific person, or the entire company? so either i spend time selecting the exact users for over 400 different workflows. OR i share it with the entire instance and everyone has access to everything in a giant never ending list? We need to be able to share with specific groups and specific teams, Exactly the same way that all the other sharing permissions operate.   

Description - Have the ability to iterate (list method) in calculated fields, the same way it can be done in reports using text mode.Why is this feature important to you - This feature would be valuable as it enables users to reference Workfront objects that are directly related to the one they’re currently working on. It ultimately enhances efficiency and clarity when managing interconnected Workfront objects. How would you like the feature to work - the same it is currently working on reports. Current Behaviour - Is not feasible

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

Description - Did you know that Requesters cannot "Add Image" in an Update? I didn't, until a requester asked me why that was missing for them! Why?? Why is this feature important to you - Consistency of user experience, and there is no reason that a Requester should not be able to use this same functionality with UpdatesHow would you like the feature to work - Same as it works for every other access levelCurrent Behaviour - Requesters cannot use the "Add Image" when making an Update

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. 

Description - The limitation of 2,000 returns on the external look up field prevents us from being able to use master data for client names in WorkfrontWhy is this feature important to you - Using an external look up field to allow users to choose from a golden record for our client names would provide more  robust reports in Workfront.How would you like the feature to work - We would like Adobe to increase this threshold as 2,000 returns is very limiting. A query search allowing more options would support our use of golden records for robust filtering.Current Behaviour - the look up field returns the first 2,000 lines only and ignores anything after that. Our master data platform can return up over 16,000 records in 1.8 seconds but they cannot be accessed beyond the first 2,000.

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.

FEATURE : As a light/contributor/standard user (Reviewer and/or Approver), I want to be able to tag in a comment another user who is not in the workflow. This person should then be able to comment the proof but not make any decision Currently, in Adobe Workfront Proofs, users can only tag (@mention) individuals who are already explicitly added to the workflow (as a Reviewer or Approver).If a project team member needs quick input, clarification, or a second opinion from a colleague who is not part of the pre-defined workflow, they cannot bring them into the proof directly via a comment. Instead, the user has to manually reach out via email/chat, export screenshots, or request an administrator to modify the workflow and assign permissions—all of which creates friction, delays feedback loops, and disrupts collaboration. Business Impact & BenefitsAccelerated Review Cycles: Eliminates bottlenecks caused by rigid workflows, allowing ad-hoc subject matter experts to weigh in quickly witho

Our users have been getting these marketing popups quite regularly in Workfront. A lot of these events are aimed at Admins or users who have very different roles in Workfront.  Is there a way we can disable these messages? If not, can a toggle be added?  

DescriptionImprove Timesheet Behavior for Manually Pinned TasksWhy is this feature important to youCurrently, manually pinned tasks remain on a user's timesheet even after being marked as Completed or Cancelled. This can lead to confusion, as users may continue logging hours on tasks that are no longer active. It also affects data accuracy and time tracking consistency.How would you like the feature to workWe suggest enhancing the timesheet functionality to better handle manually pinned tasks by:Automatically removing pinned tasks from the timesheet once they are marked as Completed or CancelledPreventing time entry on tasks that are no longer active, regardless of manual pinningIntroducing configuration options to restrict manual pinning based on task statusAllowing system administrators to disable the manual pinning feature (Alt+P) for specific user profiles or globallyCurrent BehaviourUsers can manually pin tasks to their timesheet using Alt+P or the pin iconPinned tasks remain visi

Description - It would be helpful to have an On Hold (ONH) status for Tasks like there are for Projects and Requests. Why is this feature important to you - Sometimes tasks need to be put on hold as priorities change, etc. We'd like to indicate the true status because it's not New, In Progress, or Complete.How would you like the feature to work - Choose On Hold from the Status dropdown menu and remove it from being factored into the Project Condition. Current Behaviour - Tasks have three options New, In Progress, or Complete. We created a custom On Hold status, but it affects the Project Condition, so we adjust the dates repeatedly until the task is re-engaged and changed to In Progress or Cancelled (another custom status created.) For Cancelled Tasks, we can delete the task but it's useful to show the task was considered for the project. We remove dates and planned duration/hours for it so it will not impact the Project Condition. We don't want to remove them from On Ho

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.

A helpful and efficient update that would help reduce the number of fusion scenario runs and modules needed after an Adobe Workfront Watch Event (instant) would be simply to include numberOfChildren as an Event Filter option for Task events webhook configuration.   We are looking to drive automation once a task status changes but looking to limit the run on only actual tasks, not parent tasks.   We are able to work around but see double the number of runs necessary and need to add extra modules to read the task after the webhook.   This would be similar to this idea where the option to filter by that field for task objects:  Fusion Watch module for a task canStart update | Community  

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.