Adobe Workfront

Description - The filters you create in the Workload Balancer do not become available in other areas where the workload balancer is embedded. If you create a filter in a Project's Workload Balancer, it's not available in a Teams Workload Balancer of the Resource Management page's Workload Balancer.  Instead you have to create everything from scratch in each area that you are interacting with the Workload Balancer.   Why is this feature important to you - Cuts down on the amount of rework needed for creating and sharing filters. How would you like the feature to work - If you are creating a filter for the Workload Balancer that filter should be accessible on any of the pages that the Workload Balancer is embedded on. Current Behaviour - If you create a filter for the Workload Balancer in the Resource Management page, that filter is not automatically available for use when you pull up the Workload Balancer in a Team page or a Project page.  If you want

Description - Similar to this old idea, it would be helpful to configure approvals based on a few more options. Why is this feature important to you - We're always looking for ways to reduce the number of clicks a user has to make. In our case, we have an intake process that is purely approval-based. Without approval logic, my decision-maker must also close the request after approving. How would you like the feature to work - Allow logic to define what happens upon approval (ex. upon approval, close this issue). Also prompt the decision-maker to provide comments and have those comments appear in the object's Updates. Current Behaviour - For an issue approval, we can only define what happens when the issue is New and then when rejected.

Description - Assigning approval flows to be used by certain groups is helpful for group admins. It also allows easier auditing of approval flows by who is using them. However, when we have separate request queues that are owned by different groups, they need unique approval flows. Several of our request queues send approvals to the same type of person. Why is this feature important to you - I have to create copies of approval flows for child groups. Then, when approvers change, I have to update multiple approval flows. Yes, I could workaround this with a Team, but when there is just one approver, a Team is extraneous. How would you like the feature to work - When an approval flow is set to be used by a certain group, any child groups should inherit the ability to use the approval. Current Behaviour - Currently only specific groups can use their approval flows.

Description: The update to the Custom Form Field Logic in version 25.4 introduced some frustrating issues. Clicking 'Add Logic' opens a full-screen view unnecessarily. The primary concern, however, is that the Field Name is no longer displayed—it only shows the front-end Label.Why this feature matters to you: When working with multiple fields, being able to see the Field Name serves as a valuable point of reference, especially when using numbered references for better organization.Desired functionality: The feature should operate in a smaller view screen while ensuring the Field Name is displayed alongside the front-end Label.Current behavior: The logic editor opens in full screen and does not display the Field Name.Example:   

We are on a Quarterly product release schedule and in the upcoming "24.7" Release, Adobe has stated that they will be replacing the legacy form builder with the new "Form Designer".  In the legacy form builder, for each field, we have ability to enable the option "Track field changes in update feeds".  This option was removed from the new Form Designer and now the only way to set this option is from the Interface tab under Setup.  (Setup > Interface > Update Feeds > Tracked Fields > Custom Fields).  I submitted a ticket to Support, and received the following suggestion: If you would like to see this checkbox to track these fields be retained within the Custom Forms area as it was in legacy, please submit this as a feature request via our Workfront community on our Experience League site. So here I am, requesting that this ability be retained in the new Form Designer tool.  Please!  

Idea:   Allow ability to expose project level information on a request or issue form.   We have a need to expose things like dates that allude to key deadlines or even things like key project data when submitting through issues on in process projects.  This would help create much more flexible use of calculated fields and functionality that appears to be essentially there already. Current behavior:   There is already the ability to add a calculated field to a form that reads from the project level, but this simply is just not updated (or calculated) until after the form is submitted.    How could this work?  The idea would be to turn on the dynamic calculations or even simply calculate upon opening of a queue topic form to expose the current values.    The amazing thing is this essentially already works today! Just need to have a calculation upon opening to capture the data from other objects levels! Attached a

Description - Currently the "Post as update..." message shortcut in Slack App does not accept links or show the name of the @mention tags making the feature to lost part of the relevance since people want to understand who is being tagged (we just see a bunch of codes) and also it simply removes any links from the post update.Why is this feature important to you - with the ability to share a Slack update on Workfront we want to make sure to understand who was tagged and also which links were shared. Currently we're not able to see that, which loses the need for us to connect the update to Workfront.How would you like the feature to work - When we post a Slack update to Workfront, I'd like to bring the name of the person that was tagged and also any links that were shared in the update.Current Behaviour - Currently the "Post as update..." message shortcut in Slack App does not accept links or show the name of the @mention tags making the feature to lost part of the relevance s

It would be useful to be able to delegate work to multiple people. I am in an agency environment and one person may support multiple accounts (portfolios in our instance). When they are out it would be ideal for them to be able to say delegate tasks in this portfolio to person 1 and in this portfolio to person 2. 

Description - Make the task description and project description fields formatted text field types instead of paragraph field types so that we can link, bullet, bold, and use italics. Why is this feature important to you - I always add links to reference documents in task and project descriptions and the full URLs make the field really long and hard to read.How would you like the feature to work - Change the field type from plain text field to formatted text/enable rich text formattingCurrent Behavior - can't format text in task or project description at all. 

Description - Once a request is converted to a project and assigned, it would be helpful if there was an option to "lock" the original request.    Why is this feature important to you - Often, those who request projects add updates or documents to the original request versus the project and forget to @ whoever they are trying to communicate with, and those comments or documents are missed.    How would you like the feature to work - Once converted, the request is locked (automatically would be preferred) but could also include an option for System Admins or Project Managers to unlock or make a change if necessary.    Current Behaviour - I have found a workaround for this within the dashboard (removing the link to the request) but it is much too easy for requesters to click on "Requests" and then click the original request, which then leads to the original issue. 

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

Description - A user should be able to set the the default number of hours that a request will take IN ADDITION to the Default Duration that can be set. Currently, if hours are used to describe the Default Duration, the Request will have a start and end date/time based on those hours. However, Requests should be defined by both the Planned Hours set (e.g. 2-3 hours of working time) as well as the total Duration of the Request (e.g. 3 days). If a user chooses 3 days as the Default Duration, the system assumes that the assignee will allocate 24 hours of working time to complete the Request. If a user chooses 2 hours as the Default Duration, the system assumes that the assignee will be done with the Request in 2 hours time. The system should account for both forms of timing.   Why is this feature important to you - As Requests are made, the incorrect Planned Hours based on 3 days of duration are assigned to the working team member. These hours, while not accurate, often spike th

Description -Our team relies on commit dates to plan out and communicate our workload every morning to our lead. This helps us know if we are able to take on more work or if we need to push out work. Having easy access to it is very efficient. The process we had in the updates tab was a simple dropdown 1 step process that was separate from the completion date which made it easy to identify it and update it.