Adobe Workfront

If I have a PDF with comments in it, the comments are unable to be imported along with proof uploads. We often times receive files from our vendors or authors where they commented and we need to route the PDF and comments for internal review. It will be very helpful if the comments can be imported with the PDF during proof uploads.

The Problem: Displaying inactive users creates a poor user experience when trying to confirm if object is shared or not. Currently, active users are mixed alphabetically with "No Access" or inactive users, forcing our team to scroll excessively and manually click the "X" to clean up share list. This manual maintenance is a time-sink, diverting our team from their primary goal: supporting our customers.Requested Enhancements: Collapsible or Hide "No Access" View: implement a collapsible section for users with no access, similar to how inherited permissions are handled. Users should have the "choice" to expand this list via a toggle (>) only when needed.  Automated Team Offboarding: way to automate the removal of inactive users from Teams. Currently we either have to have team owner go and remove or our ops team need to go into the user and X all the teams they are tied to.  Again takes away from our doing our day to day jobs. The Goal: Minimize administrative overhead so our team c

We would like the ability to display specific dashboards at the project template level.  Our projects are at the individual deliverable level (i.e. an individual print piece, email, web page etc.), and we have templates for the different medium types.  We would like to be able to add custom dashboards that provides specific information for that particular medium type.  So for the print template, we have the print dashboard, for the email template, the email dashboard, and so on.  The source information for the dashboards will be from the project details, but the dashboard/reporting will allow us to highlight specific information.

Idea:   Enforce required fields on custom forms and do not allow a task to be completed before they are populated.      There have been several of these ideas in the past but really wanted to bring this back up in a newer idea forum as this is a huge concern coming from a highly regulated industry.    I would really anticipate that this impacts almost every organization that uses Workfront as this is really expected behavior when you indicate that a field is required.    Idea option 1:   Required * = field must be populated before status can be moved to complete. Idea option 2:  Could we potentially add an option for “Required to close” checkbox when designing a custom form field; a second required checkbox option that drives different types of required action. This would mean you could leave the current structure as is, but simply expand to enforce required nature upon the task completion trigger. Current Functionality:   If a form is not opened to edit mode, the application does not

A portion of our end users access Workfront via iPad. While testing, I confirmed that the time field within the date field is functional; however, it requires time to be entered in an exact XX:XX AM/PM format, which creates a poor user experience on mobile devices.Given the volume of iPad users on our team, I recommend Adobe revisit the time field input to support a more intuitive editing experience, such as a scroll selector or auto-formatting, to reduce friction and improve usability across devices.

I wanted to suggest an improvement regarding how we handle delegated issues in Workfront. As it stands, unless a delegate user takes ownership of a project, the delegated issue will only appear in their "my work" widget. This setup isn't quite streamlined enough for our needs. Could we request to have Workfront include delegated tasks in the "my task" widget as well? This adjustment would provide a more cohesive and efficient view, allowing us to better track and manage our responsibilities. Thank you for considering this suggestion. Looking forward to your thoughts on this matter.

What do we need:Create or update a user notification option that lets assignee(s) know when a task can start work!  (Can Start = True = Notification)                                        My Ask → Please Upvote this idea! There is currently not an option for users or admins to enable a notification to be sent to a user or team that is assigned to a task that lets them know that they can start working on a task; a trigger once the Can Start indicator on a task moves to True.   Users do not receive notifications that let them simply know they can start working on their task.   What’s available today in user notifications?   There is an option for “All predecessors of my tasks are completed” located in the Information about Work Assigned to Me section, but this does not always work and is not always accurate.  This runs simply off directly associated predecessors on a task.  If you manage predecessors at a parent task level, notification will not be sent to your users and affect your tea

One challenge many users face across Adobe products is navigating documentation, tutorials, and community resources efficiently. Even though Adobe provides extensive documentation, finding the exact answer quickly can still require multiple searches across help pages, forums, and external tutorials.Proposed Idea:Introduce an AI Documentation Agent embedded directly within Adobe Help, product panels, and community pages.This agent could allow users to: Ask natural language questions about features or workflows Instantly search and summarize official Adobe documentation Surface relevant tutorials, guides, and community threads Walk users step-by-step through tasks directly inside the product Suggest related features users might not know exist Example Use Cases “How do I remove background noise in Premiere Pro?” “Show me how to create a gradient mesh in Illustrator.” “What’s the difference between Smart Objects and Linked Objects in Photoshop?” The AI agent could return: Direc

When a user copies a URL from within Workfront (e.g., via 'Copy URL' in the Documents folder menu), it pastes as a raw URL with no display name — exposing a long string of alphanumeric IDs that is hard to read and unprofessional when shared in tools like Slack, Outlook, or Teams.Current Behavior:Pasting a copied Workfront URL displays the full raw URL. Example:https://companynamehere.my.workfront.adobe.com/issue/11aa11a0001123456df123dfcc1e1234/documents?initialFolderID=11b01cbf00010123bb12345ac12d123dAdditionally, there is no 'Copy URL' option on project or task pages, so users have no native way to share a direct link to those objects, other than copying the raw links from the browser address bar.Desired Behavior:1. Copied Workfront URLs should carry a friendly display name on paste — such as the document name, object name + ID, or folder path + document name — similar to how Microsoft Teams handles copied links.Pasted Teams link comes with Display text2. A 'Copy URL' option should b

Within the Fields library you have columns:Name Type Instructions Display Type Active/DeactiveCurrently, there is no way to add a description column for fields. This makes it difficult to document important information about each field within the system.A description column would allow administrators and developers to include key details about a field, such as what the field represents, backend or integration-related notes, data source information, or other relevant technical context. This type of information is different from user instructions and is intended to provide internal documentation about the purpose or structure of the field.Having a dedicated description column would improve clarity, reduce confusion, and make it easier for teams to maintain and understand complex forms or datasets over time. It would serve as a central place to store field-specific metadata that is currently difficult to capture within the existing interface.

Add a Full‑Screen Toggle for Proof ViewerAdd a button that allows the Proof viewer to be displayed in full‑screen mode. With the new unified experience, both the Adobe and Workfront toolbars occupy space at the top of the screen, reducing the available viewing area. Our editors would find it much easier to review Proofs if they could toggle into a true full‑screen view and see the content at full size without interface distractions.

This feature was recently removed. Now if I happen make a change to my document and require the approver’s decision again, I have to remove them and then re-add them. This will trigger an email to the approver saying “Your approval is no longer required.” followed by “Your approval is required” which is extremely confusing. From a user-experience standpoint, the removal of this option is a step backwards. It was a feature up until a bug was fixed. Why remove a feature?