Adobe Workfront

In Planning, connected fields have Record Filtering Rules. When you are in a table and you click to select from the connected records in that field, you are only shown the ones that meet the criteria for those rules. Great feature!  However, it does not apply to a Request Form built for that table. The filtering does not apply. AI Coworker confirmed this and said the best workaround was to manually filter your data set. That’s not good enough.  I badly want to be able to apply filtering rules to connected fields/records in Planning. It seems like an oversight that we can’t do this now. 

Description - Would love to have the option to pin and unpin a certain update to the top of the updates thread. This would allow for easy visibility on the most up to date items, etc. Would also love the option to filter updates by date, time, etc. to quickly search through and locate a certain update.  Why is this feature important to you - This would increase productivity within the Workfront platform tremendously and would avoid confusion and clearer communication with cross-functional partners looking for information via updates. How would you like the feature to work - A button that says "Pin" next to "Reply" and " Like" - Once pinned there would be an option to "Unpin" For the filter, some sort of filtering option at the top right of updates then you can click and customize certain date, time, latest comments, etc)  Current Behaviour - Updates are ordered in the time in they are posted, and all replies and updates are not able to be customized at thi

Problem StatementCurrently, Workfront hour reports and views provide visibility into who updated an hour entry, but there is no native field to easily identify the user who originally created/entered the hour entry and the timestamp.Why This MattersAudit trails require knowing the exact origin and timestamp of an hour entry. Without a "Entered By" and a "Timestamp" field auditing and troubleshooting time tracking discrepancies become unnecessarily difficult.Example: We have integrations that enter hours from Salesforce to Workfront, which a user can later update. So, it is important to have both the information (entered/updated). I can use a Journal Entry but that is a waste of time and becomes difficult to explain to process owners.Proposed SolutionAdd the following native fields to the Hour Report: "Entered By": Displays the user who initially submitted/generated the hour entry record (independent of who last updated it). "Date Created / Timestamp" (Journal Date): Displays the exac

When using the 'updates' function or tab, it would be useful for our teams to be able to utilize this space in a fashion similar to email. IE- to add colored text to responses, in order to differentiate between users. Also, it would be helpful to allow certain updates to be 'pinned' to the top of the page so they don't get lost. OR to categorize them as "bulletins or job notes" of some kind to set them apart from the back and forth threads.

We get a lot of the busy projects with multiple comments and updates posted daily. Some system comments or Summaries or updates are super important and we want to be able to PIN them and Highlight or have a way to view Important notes only. 

When an image is uploaded in the comment section of an issue or request, it should be automatically replicated and remain visible after the request is converted into a project. This will ensure that all relevant visual information and supporting documentation from the issue-level comments are retained and accessible at the project level.

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.

Current state, only AND condition available Idea:Currently, when building automations in Workfront Planning, trigger conditions across multiple fields only support AND logic. This means all conditions must be met before the automation runs.It would be extremely valuable to have the ability to use OR conditions as well.Example: Trigger an automation when:Status = Approved OR Priority = High OR Type = Urgent RequestToday, the only option is to use AND logic, which significantly limits flexibility and often requires creating additional automations or workarounds to achieve the desired outcome.Business Value:Reduces the need for duplicate automations Simplifies Planning configurations Supports more real-world business use cases Makes automations easier to maintain and scaleAs organizations start adopting more complex Planning setups, OR logic would make automation capabilities much more powerful while keeping configurations simple and intuitive.Use Case: A marketing operations team wants t

There should be a way to archive records that have a certain status, like Completed or Canceled, for example. Once an organization moves beyond test use cases, the records of a real enterprise start to add up. To my knowledge, Planning comes without a way to move/remove ‘archived’ records from record types, especially connectable record types. My solution for now is to just put ‘z_archive’ on the front of each records name. I could probably build an automation for this but I’d rather this be a feature of Planning.

We'd love to use Workfront Planning for asset tracking and management, but currently there's no way to store files or images directly within a record, aside from the thumbnail.Adding an attachment/document field that supports multiple files and images, similar to Airtable's attachment field, would make Planning much more useful for asset management. This would allow teams to keep asset details and supporting files together in one place instead of relying on external links.Interestingly, Workfront AI Assistant already suggests that this functionality exists, making it feel like a natural addition to the platform.

With the way Workfront Planning is expanding, do you think there is a need for a separate topic specially for Workfront Planning within Workfront product community? 

With Internal Lookup fields replacing Typeahead fields in Workfront, I would like to suggest an improvement to how dropdown options are displayed within reports.Previously, Typeahead fields allowed users to easily view the full name or description of each dropdown option without requiring excessively wide report columns.Currently, Internal Lookup fields display dropdown options within a limited width, making longer names or descriptions difficult to read. Increasing the column width to accommodate this information takes up valuable space and negatively impacts the overall report layout.Proposed Enhancement:Allow Internal Lookup field dropdown menus to automatically expand beyond the report column width, similar to how Workfront's native fields (such as User fields) currently function.This would allow users to view the complete names or descriptions of dropdown options without having to widen report columns.Benefit:This enhancement would improve readability, usability, and reporting eff

Convert the programs page into a widget that can be added to WF Home. This would allow convenience of accessing that page without leaving Home and allow project managers to quickly search for programs they need to access

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. 

Provide a native Workfront notification capability for asset status changes in AEM Assets.ProblemWhen an asset submitted from Workfront changes status in AEM Assets, the user who originally uploaded or submitted the asset should receive a notification in Workfront. The notification should be configurable so customers can define whether notification is required and/or which asset status changes should trigger a notification.A two way Fusion integration between AEM Assets and Workfront can be used today to sync updates between the two systems. However, there is currently no native notification capability for the Workfront users to track the status change. ImpactThis would provide better visibility into the asset lifecycle and reduce the need for users to manually check asset status or coordinate with other teams. It would also allow users to take immediate action when an asset is rejected or requires changes, reducing delays in the content production and approval process.

Native dependent dropdowns in custom forms, where an admin defines which child options are available for each parent value, and the child dropdown shows only those options at runtime. It should work with forms used on projects, tasks, requests and documents, so the values map cleanly to AEM metadata. Problem StatementIn Workfront custom forms, a dropdown can't limit its choices based on the value picked in another dropdown. Form logic can show or hide fields, but it can't filter the options inside a dropdown. Validation logic can block an invalid combination, but users still see every option and only find out after they choose wrong.ExampleA manufacturer's form has two fields: Model Range and Model Derivative. When the user picks Model Range = Range A, Model Derivative should only offer the derivatives that belong to Range A. Today it shows all of them, and nothing stops the user picking an invalid pair at runtime.  ImpactUsers can submit invalid combinations, such as a derivative that

Currently, when sharing Adobe Workfront ( as well as Firefly and Express) links through Microsoft Teams and Outlook, the links are not distinguishable from each other, which makes searchability and quick referencing a challenge. It would be amazing if those links could be prepended by the Project Name or for it to display in the image preview. 

When the duration of a Task or Issue exceeds 1000 days, Workfront's Workload Balancer and related services reset or fail to evenly distribute planned hours across the entire duration. This is not due to the total number of planned hours, but specifically the duration threshold. The Workload Balancer documentation mentions that allocations display as zero after the 1000-day or 1000-hour limit is reached, but does not explicitly clarify that you cannot continue allocating hours beyond this limit. It is recommended to break Issues or Tasks that span longer than 1000 days into smaller, sequential Issues/Tasks (e.g., annual or biannual segments).This is a design flaw and needs to be remediated.

The most common complaints from my company’s users are the number of emails they recieve, not receiving notifications when they should, or not receiving the same emails as their coworkers. This is often caused by mismatches in notifications settings between users, with the root cause of the issue being that the admin must update each new user’s notification settings manually.It would be extremely helpful to have a system-wide notification settings where individual notifications can be turned on or off, and set to instant or daily, then those settings would apply to all new users.

As an admin who handles licensing and onboarding of new users in an instance with many teams, groups, and multiple companies, it would be very helpful to be able to see a user’s groups, teams, and company from their details section.Having the ability to add any user field to the details area, would save me several clicks and scrolling to update a user’s team, group, or company, especially when I’m onboarding several users at once.

WorkFront has no ability to 'undo last action' - in some cases this can be very troublesome - as it is quite easy to make a change to basic project behaviour, critical path and end dates. An 'Undo' last change function would be very useful if the Project owner has in-advertantly made a change that has caused multiple activities to be impacted. Even a - revert to last saved version function might be useful - at least allowing the project owner to go back to a version that they have already reviewed and approved with their team.

We have observed that there is currently no reporting capability available to track AI Assistant usage and adoption.From an operational, governance, and business value perspective, it is important for Business to understand how the AI Assistant is being utilized across the organization. At present, we are unable to determine key metrics such as user adoption, usage trends, interaction volume, or overall utilization of the feature.We would like to request that Adobe consider adding a Workfront AI Assistant Usage Report feature that provides visibility into:Active users of the AI Assistant Usage and adoption trends over time Number of AI Assistant interactions/prompts Group, team, and organization-level usage metrics Dashboard and export capabilities for reporting purposes API access to usage data, if availablePlease let us know if such reporting capabilities are currently available, planned on the product roadmap, or if this request can be submitted as a formal product enhancement to th

Something that should be table stakes - but is not is the ability for users to only see their requests from Project Intake.We did find a nice use using the Home widget - but there’s 2 issues with this that would make great enhancements:If a user is on the New Experience and they have switched to New Home experience - it provide proper limited visibility. Allowing ability for Group Admins to set the default User experience for their users would be a great enhancement.OR just allow the ability to remove the “ALL Requests” Filter from Requests OR Home Widget 

Description - Before the migration to Adobe console, we were able to have two email addresses associated to each Workfront account. One email (FedID) is what our users used to login through SSO and the other (Username) is where their email notifications from Workfront went. With console this is now no longer possible and support has been unable to suggest a workaround. Would love to see this functionality restored! Why is this feature important to you - Some of our users need their notifications routed to a shared inbox for coverage purposes/so it is easy to jump in and help each other with workloads.  How would you like the feature to work - I would like to be able to have a field on the user profile again where I can input an email to send Workfront notifications to.  Current Behavior - Functionality no longer exists.

As we roll AI Form Fill and AI Assistant out to our organization, we’d love the ability to create and add to a prompt library, or work to establish a general prompt library across Workfront instances. Given our end users all operate differently, there’s enough variability that we can’t pin down what they may input and what the AI Form Fill tool may output as a result, so establishing guidelines/prompts feels like a great starting point.