Adobe Workfront General

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

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! 

While I tried to filter users, I set the option EmployeeCode, and selected “Is Any Of” and pasted 1000 user employee codes, it broke the page. It should not be like that, if it cannot process the filter it should show a warning or say something instead of being unusable, even when reloading the browser did not work.

My team needs to see more information on cards within boards. Simple interface improvements would make a hugeeee difference! Improve colors (not just a little box) See planned hr/story points See status of tasks under that card

Problem StatementCustomers are reporting color discoloration and washed-out rendering in Workfront Proof that does not match the original processed creative assets. This issue is particularly visible in color-sensitive review and approval workflows where proof accuracy is critical for validation and sign-off.The issue appears to be related to changes previously made to support overprinting and multi-layer PDF rendering. While the prior enhancement resolved a separate issue involving varnish and multi-layer content not rendering correctly (Reference: #00442736 - Environment Discrepancy: Varnish Layers Failing to Render in Capital One Proofing Viewer), customers are now experiencing color discrepancies that may be an unintended side effect of those rendering adjustments.Business ImpactReduces trust in Workfront Proof as an accurate representation of final creative assets. Creates confusion during review and approval workflows. Impacts customers with color-critical use cases, including pr

We would like to move to Adobe Cloud Storage so we can take advantage of the new Unified Approvals with Frame.io. However, doing so would require us to manually recreate all of our Workfront Legacy project templates—more than 200 in total. While I understand that projects can be created manually from a legacy template, that does not meet our needs because we use Fusion and Kickstart to load most of our projects. In addition, each template includes required fields within forms that cannot be completed until the project reaches specific tasks. Currently, there does not appear to be a way to manually create a project without completing all required fields. The folder structure also does not carry over to a cloud project, so that would need to be recreated manually for each project. Is the ability to copy project templates to Adobe Cloud Storage on the roadmap? If we need to recreate the folders manually, that would be manageable; our main concern is avoiding the need to manually rebuild m

My team has noticed that Workfront now defaults to showing AI Suggestions when attempting to link AEM folders to Workfront projects. The “suggestions” take up most of the screen and make it harder to find the folders we’re looking for (even when we “hide” the suggestions). Additionally, more often than not, we are “hiding” the suggestions as they are not very helpful. It would be nice if we were able to turn this feature off while retaining access to other AI features in the application. Ideally, this would be a setting that the user could change in their preferences (rather than turning the feature on/off across the whole organization). 

When creating Layout Templates in the New Workfront Experience, we're currently limited to only being able to pin Main Menu Items or Dashboards. Ideally, we should be able to pin specific Objects on a layout template (Project/Portfolio/Report/Document/etc.).

Custom Forms are an important use-case. Many users have a need to see and/or input the Custom Form, but do NOT need to make four or more mouse clicks to get there. The current Layout Template "Tabs" feature exists, but can only incorporate "Dashboards." This proposal is to add a "Quick Pin" that allows System Admins to create/edit a Layout Template to attach a specific Custom Form. This means that a specified user could have a default view that is directly and specifically to a Custom Form.

Description -Enable any URL to be added as  pin on the layout template page.Current Behavior -Currently, from the layout template, we can only pin dashboards or standard pages also accessible trough the "Waffle Menu".Why is this feature important to you -This has introduced the need for admins to go in to every new user and manually pin a specific board to their home page.How would you like the feature to work -At the layout template page, allow users to enter a URL to the pins. 

Description - While viewing all Project Tasks, having a dedicated Field/Column for logging Task HoursWhy This Feature is Important - Having the ability to log hours directly from the Project Tasks page and not needing to navigate to either the Task itself, or the Open Summary tab would be incredibly helpful. This would reduce User effort in logging time, while also removing any possible confusion for new Users navigating to the Task, and back to the Project, or navigation within the Open Summary tab.How the Feature Would Work - Added Field/Column to the standard Project View as a place for Users to log hours. This could be done via a button similar to the Status Icons that directly opens the ‘Log Time’ panel (without leaving the Project page). Alternatively this could be a Field where Users enter a numerical value that is then added to their Actual hours, and then removed from the Field. Current Behavior - Currently, Users need to navigate to the Task itself to log hours, or use the Op

One of the challenges we're trying to address is the amount of manual effort required for users to complete and submit multiple intake forms in Workfront at a time. To help streamline this process, we are exploring a solution that would leverage a custom web service and Workfront APIs to help automate the completion and submission of custom forms. The goal is to enable users to submit multiple intake requests programmatically while still adhering to the business rules and user experience defined within the Workfront custom forms. As part of an enhancement feature, would it be possible to allow API access to the display logic (e.g., cascading rules/conditional visibility) and/or other methods to retrieve the display logic within the custom intake forms?

Description - Would love to have the option to attach a file to a request in Planning.Why is this feature important to you - We thought we had a solution to our public facing request problem through Workfront Planning's ability to create public request links. However, the inability to attach files makes it a non-viable option for us.How would you like the feature to work - Just like in Workfront Core, we would like to have the option to attach files to requests.Current Behaviour - Currently there is no file attach option in Workfront Planning.

SummaryOur team uses Claude connected to the Workfront MCP server to answer resourcing questions in natural language. Planned Hours are fully and reliably queryable today. Remaining Available Hours — the metric the Resource Planner itself calculates (schedule capacity minus time off minus existing commitments) — is not exposed through any MCP tool, and cannot be reliably reconstructed from what is exposed. We're requesting this data be made queryable so a team's full capacity picture (Planned + Available) can be surfaced through natural-language requests, not only through the Resource Planner UI.What Works TodayPlanned Hours are cleanly queryable via the insights_find_workfront_data tool, using fields such as assignment.assignment_workRequired and task-level planned hours, grouped or filtered by user, project, or date range. This lets Claude answer questions like "how many planned hours does each person on this team have this month" accurately and immediately.The GapThe Resource Planne

In the new unified approvals, when an approval template is created, there is a field for “workdays until due date”. We need this number to exclude weekends, or at least have the ability to associate with a schedule that excludes weekends, so that approval due dates do not fall on weekends without manually adjusting the due date with the calendar feature.

It would be great if the Date field could be customized, such as being able to block or highlight specific dates when the calendar pops up.  

Currently when you unassign a user from a task/issue, it automatically fills in the assignee with that user's job role. My company has never used this feature and it just creates extra work and confusion to either remove that job role or to see it in the assignments. It would be great if this is something we could disable in the setup area.

Add function to API to add nonWorkDay (NONWKD) without needing to nest beneath an object with all other nonWorkDays. Right now to add a nonWorkDay to a schedule all existing nonWorkDays must be collected first as an array. Then the array must be added to with new dates to an edit call on the parent object. The longer the schedule is used the larger this array becomes the harder it is to confirm no errors or missed dates.