Skip to main content

Filter by idea status

10000+ Ideas

Favorite Users & Teams for Streamlined Task AssignmentsNew

Dear Adobe Workfront Innovation Team,I would like to propose a feature that would enhance efficiency and accuracy in Workfront: the ability to create a “Favorites” list for users and teams within task assignments and tagging functions.DescriptionIn many workflows, users frequently collaborate with the same individuals or teams. However, Workfront currently requires searching through the full user directory every time a task needs to be assigned or a colleague is tagged. This can lead to misclicks, slowdowns, and inefficiencies, especially when users have similar names. To streamline this process, I propose a "Favorites" List that allows users to mark colleagues or teams they work with most often for quick access in assignments and tagging.Why is this feature important to you?This feature is crucial for improving workflow efficiency, accuracy, and user experience:Saves Time – Reduces time spent searching for frequently assigned users.Minimizes Errors – Prevents misassignments caused by selecting the wrong person with a similar name.Enhances Productivity – Allows users to focus on work rather than repetitive administrative steps.Improves Usability – Makes Workfront more intuitive and personalized for users with high-volume task assignments.How Would You Like the Feature to Work?Users can mark individuals or teams as Favorites from their profile, a dropdown menu, or the People section.When assigning tasks or tagging users, Favorite users appear first in search results or in a designated section at the top.The Favorites list is customizable—users can add or remove people based on changing workflows.This feature could be an optional toggle for users who prefer to keep the full directory view.Current BehaviorCurrently, Workfront requires users to manually search for individuals each time they assign a task or tag a person in comments. This leads to:Increased time spent scrolling/searching for the right user.Risk of selecting the wrong person, especially when names are similar.A less personalized and efficient workflow experience for users with recurring assignments.By implementing a Favorites feature, Workfront can enhance efficiency, reduce errors, and improve overall user experience—helping teams stay focused and productive.I appreciate your time and consideration, and I look forward to your feedback!Best regards,Mirella B

Fusion Displaying Non-Editable Descriptive Fields as EditableNew

DescriptionWhen using the "Update a Record & Attach a Custom Form" module in Fusion, descriptive text fields appear as editable fields in the interface, even though they cannot actually be modified. This is misleading, as descriptive fields are intended to be static and only serve as instructional labels. Their presence in the module creates unnecessary noise and can cause confusion for users who might assume they are modifiable. Why is this feature important to youDescriptive fields are meant to provide guidance and context within custom forms, not to store data. Showing them as editable fields in Fusion is misleading and could result in users spending time trying to modify them, only to realize that the changes do not take effect. This clutters the UI, making it harder to focus on relevant, actionable fields. Removing them from the update module would improve clarity and streamline the user experience. How would you like the feature to workFusion should recognize descriptive text fields as static and exclude them from appearing in the "Update a Record & Attach a Custom Form" module. Since these fields cannot be modified, they should not be displayed alongside other editable form fields. This would reduce UI clutter and prevent confusion for users working with Fusion automation. Current BehaviorCurrently, Fusion displays descriptive text fields as if they were editable when a custom form is attached via the "Update a Record & Attach a Custom Form" module. However, even though they appear in the UI, they cannot actually be modified. The only way to change these fields is by manually editing the custom form via Setup > Custom Forms. Their presence in the module is unnecessary and can be misleading.

BenKuhnNew Participant

Add a "Preferred Name" option for accounts using SCIM and SSONew

Description -  Please add a field/claim for user's preferred names that can be populated with SCIM or OIDC/SAML. Why is this feature important to you -  The current implementation requires a given name and family name.  Accounts that are provisioned with SCIM reset any changes the user may make to their name field.  We have employees who go by their middle name, or prefer a different name.  We also have employees from cultures that don't have legal family names which causes issues with the current system that requires a family name.  We are working around this by passing the user's preferred name as the given name and using anon-printable character as the family name, but the non-printable character is causing a bug that is preventing other fields from being modified.  Rahul Yadav from Adobe support says that this is not a bug and everything is working as intended and is refusing to provide support at this point.  It is unclear how using that character as a last name is causing issues saving other fields UNLESS THIS IS A BUG WHICH IT CLEARLY IS. How would you like the feature to work -  A field would be created for "Preferred Name" or "Display Name" or similar that could be provisioned via SAML claims, via an OIDC token, through SCIM, or edited manually by a user. Current Behaviour - There is no way to automatically provision a user's preferred name without hitting other bugs in Adobe's systems.