Currently we can add fields to the Home and Summary tab via the layout template, however, those fields are only visible to the person assigned to the object. In general when a customization is added to a layout template everyone with that layout template can see the customizations and I don't belie...
Typeahead filters should be able to be applied at the form level. For example, if I create a project typeahead field for a team and filter it by their portfolios, I should be able to add that same field to a different form and apply a different filter. Otherwise, I have to create a new typeahead f...
When I share an object, whether it's a project, report, view, or otherwise, I'd like to be able to add a short comment for the recipient(s) of the share notification to provide additional details about what is being shared, where to find it, etc.
We have an existing implementation where teams use a Paragraph Text field to document task/ project updates. A calculated field then captures the date the paragraph text field was last updated. We hoped to improve our users experience by giving them the RTF field in place of the existing paragraph...
When performing a sort by column in on project schedule, the sort sticks when navigating to another project schedule even when the field in the initial sort is not present in the new project schedule. This causes the task order to appear correctly in numerical order when in fact, it isn't. This mean...
We have many teams at Google that are being given access to online Ascent training. Currently, only one person is able to have visibility into these individuals progress. It would be ideal if we could have a multi-level management structure in the tool to allow our entire team to have the same vis...
When users change values in specific fields, we'd like to require that they provide rationale for the change in a corresponding text field. For example, if a "Planned Delivery Date" is changed (custom field that requires manual input), a custom text field "Rationale" would appear that the user is r...
When using an API call to populate native and/or custom fields at the task level, it would be nice if the call could also lock the fields to indicate changes are not possible by the users in Workfront. This allows the external system to remain the source of truth and eliminates the need to provide ...