Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

Allow External Lookup Fields to utilize a "Select All" buttonNew

Description - When using a $$HOST-based external lookup field and maintaining a data table, such as a list of US States, users currently have to click on each valid option that appears in the picklist for a multi-select-allowed External lookup field.  Why is this feature important to you - This will bring parity to the External Lookup Field with the Multi-select Dropdown field. Much of the discussion around external lookup fields is that they can be used as a dependency-driven list of results that helps control front-end user input, especially when flowing through a custom form for an intake process. This really supports staying away from the "Garbage in, garbage out" trap of users mis-selecting options in an intake process. How would you like the feature to work - When "Multi Select Dropdown" is selected in the field setup, users should be given a UI-button that responds the same way the current Multi-select options (Dropdown, Checkboxes) works. A "Select All" option should populate all of the choices that are valid for the JSON path, and then from there, users should be able to use the "x" button on the individual choices they DO NOT want to include. When the 1st option removed, the "Select All" button should also clear, allowing for it to be re-selected, and any options that were removed, should be re-added to the list within the field. Current Behaviour - Users have to click every valid option in an external lookup field result. Bonus fix/Observation!!! - The user experience when selecting multiple options from an external lookup seems to be wildly inconsistent. Some users can click a result, and the list of possible results stays open allowing them to quickly click more options to add to the selection. Other users have the external lookup dropdown interface close with each and every selection, requiring an additional click to re-open the selection field, and another click to select an item, which subsequently closes the field again.

Josh Stephens
Community Advisor
Josh StephensCommunity Advisor

Improve sorting and display of CJA bucketed dimensionsNew

Description Sorting for bucketed dimensions in CJA should default to logical sorting by the dimension's numerical value, rather than it's label. Buckets should be displayed more clearly (Less than 30, 30 to 59, 60 to 119, 120 or more) Why is this feature important to you Bucketed dimensions are intuitively understood when sorted in logical order by the value of the dimension. For example, shortest to longest time. It's confusing when two buckets are ambiguously defined and contain the same value (example: 30 to 60, 60 to 120). How would you like the feature to work Bucketed dimensions should default to logical sorting by the dimensions numerical value. At a minimum, users should have the option to sort by logical order. Example: If I have a bucketed dimension for time in seconds (Less than 30, 30-60, 60-120, 120 or more), I'd like the option to sort them logically as either:     Less than 30, 30 to 60, 60 to 120, 120 or more, or     120 or more, 60 to 120, 30 to 60, Less than 30 Bucket ranges should be clearly displayed (without any overlap) Current Behavior Sorting by the bucketed dimension sorts by non-intuitive, alpha-numeric orders either:      Less than 30, 60 to 120, 30 to 60, 120 or more, or      120 or more, 30 to 60, 60 to 120, Less than 30 Bucket ranges overlap (30 to 60, 60 to 120, 120 or more), causing confusion.

"Log Hours” on Tasks Without Granting Edit RightsNew

DescriptionCurrently in Workfront, logging hours on a task requires Contribute permission, which also grants the ability to edit certain task details (such as the task name). This creates a governance challenge for organizations that need accurate time tracking but also want to maintain strict control over task data.Why is this feature important to youAccurate time tracking is essential for reporting, resource planning, and performance analysis. However, allowing users to edit task details just to log hours introduces risks of unintentional or unauthorized changes. For organizations with strict process compliance, separating time entry from task editing is crucial to maintain data integrity and governance.How would you like the feature to workIntroduce a standalone “Log Hours” permission that can be assigned independently of Contribute access. This permission should allow users with View rights on a task to enter time without being able to modify any other task attributes. It should be configurable both in access levels and in sharing settings to provide flexibility across different teams and roles.Current BehaviourCurrently, users have Contribute access to log hours on a task. This access also allows them to edit key task details, which creates a risk of accidental or unauthorized changes. There is no way to enable time entry without also granting broader editing capabilities.

Amanda3New Member

Workload Balancer Setting - Add Color Theme functionality for Project PriorityNew

Description - Why is this feature important to you -My PMO manages projects for a Creative Studio Resource. At any given time there are more than 100 projects open. When we are looking at that teams Workload Balancer we can't tell easily which projects are running ahead or behind as there is no way to see the Priority. The Priority is a field in the Overview section on a Project under Basic Information that is an out of the box field. Today we utilize Flexible and Firm Deadline to know if the Creative Studio has more time or not for their task. They appear in green (Flexible) and red (Firm Deadline). How would you like the feature to work - If Priority was added as one of the Color Theme, then it would color code the projects on the Workload Balancer - green (Flexible) and red (Firm Deadline). Benefits - Team members can see which projects are most critical (green and red), fostering alignment and urgency. Color-coded priorities help visualize workload distribution and plan for capacity more effectively.Reduced PM time going back and forth between opening up every single project to see what the Priority is.Current Behaviour - Under Select Color theme, there are 3 options today:Default: The bars for all projects and their work items display in blue.Project: The bars associated with each project and its tasks change according to the name of the project. All tasks that belong to the project display in bars that match the color of the project. The project bars display in a lighter shade to distinguish them from the tasks. The project bars also include a project icon when choosing not to display allocations.Project Status: The bars associated with each project and its work items change to the color of the status of the project.The project status is that associated with the Group of the project. If the Group does not have group-specific statuses, the color of the work item bars is that of the system-level project status. Both system as well as custom statuses display. For information about group statuses, see Create or edit a group status.However, my team is asking for the Priority field to be added to this Color Theme options.