Adobe Workfront

Description - When building a custom form you can view fields and sections in the form library. On the right panel it will note if it is used on other forms and you can click "view related forms" to get the full list. This list is incredibly helpful as is but would be more powerful if it indicated active vs inactive forms.   Why is this feature important to you - Knowing that a field is only seen on inactive forms would quickly indicate that it shouldn't be used for the form I am creating/updating. It also tells me that if I wanted to make an update to the field (hide/show a choice, rename it, change the lable) no active    How would you like the feature to work - Even something as simple as making the inactive forms gray and keeping the active as blue would help. Or if there's more real estate adding an x icon next to inactive forms. Another idea is to split the list into two sections one for active and the other inactive.   Current Behaviour - I have to either o

Description - Need the ability to move custom fields added to cards in the Configure --> Cards area. It is already clunky and buggy, but if you have to add a new field towards the top of your custom fields, you have to delete EVERY custom field added, then add the new one, then add EVERY custom filed and update names. Almost makes it not worth using boards if you have to update custom fields on the cards. Why is this feature important to you - When designing boards and the card fields, there is a bunch of feedback given to make adjustments, so every time an adjustment is needed, it takes a large amount of effort to make these additions. How would you like the feature to work - Be able to drag and drop custom fields once they are configured to be on the cards (Board --> Configure --> Cards) Current Behavior - Does not allow for moving or re-sort custom fields once added to the card configuration

Description - Right now if there are 2 assignees on an issue there's no way to edit allocations. The only option is 50/50, and that is not great for capacity planning in WLB. Why is this feature important to you - It would make the WLB a more accurate representationHow would you like the feature to work - 1) adjust allocations within WLB, or 2) adjust % within the assignment area of the issue when editing.  

We need the ability to send out automated emails with a Dashboard attached. Currently this is only available at the report level, but my team and I have often needed to send out an entire dashboard on a regular bases, and it doesn't make sense to send out each individual report from the dashboard (too many emails). There should be a way to send out automated emails with a Dashboard attached.

Description - Rich text fields have a few oddities when they are used in an External Lookup Field interaction. Rich text fields can cause External lookup fields to fail to be able to be selected OR result in an output that is not user-friendly.   Why is this feature important to you - The more consistent a feature is in Workfront, the more likely it is that I can use it to design a useful and impactful UX for my team. How would you like the feature to work - Either bring in full support for user-friendly Rich Text results in External lookup fields, or give additional features in the setup of an External Lookup Field to allow for system admins to control the results of the field. Current Behaviour - 1. The 2,000 character limit on an external lookup field will run into a conflict pretty easily when returning the results of a rich text field which to my understanding has a 15,000 character limit. The results of a rich text field are

Description - Allow lookup field results to serve as the basis for display logic within a custom form. (Especially $$HOST-based fields) Why is this feature important to you - This would bring external lookup fields to parity with other selection-driven logic on other field types in Workfront. How would you like the feature to work - When a user makes a selection in an external lookup field, that field should be added to the list of possible display-logic and skip-logic choices in subsequent fields within the same custom form. Just as dropdown fields do today. This allows for greater control and intelligence within a custom form design process to ensure users are guided to selections that make sense for a particular end-goal. Current Behaviour - External lookup fields are not recognized by the system as valid choice for which a user can initiate display or skip logic.  

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" opti

Description -I would like to see the My Projects and My Tasks widget column show the same way project and task view shows in project pages, whether or not the user access has filter edit. Why is this feature important to you - My Projects and My Tasks filter-grouping functions the same as projects and task filter-view-grouping, for users without filter edit permissions. It would make sense if users without filter edit permissions could also see My Projects and My Tasks column, since they can see projects and tasks view.How would you like the feature to work - All users can see My Projects and My Tasks columns, without having access filter edit permissionsCurrent Behavior -Only users with filter edit access permissions can see My Projects and My Tasks columns, without having access filter edit permissions

Description - It would be amazing if the LOG ID or Error Event ID and/or URL were added to the "Add Error Handler" modules.  By defualt you only provide the fields "Type, Message, and Detail".  Adding the LOG ID to the error would be immensely helpful. Why is this feature important to you -  We use the Ignore module but still want to send private message like this - That works well, but we are then forced to search through hundreds of logs to find the right error log related to the event. If we could pass a URL to the log or an ID for the event (that we could use to create our own URL), it would be awesome and save so much time!!  How would you like the feature to work -  Add the URL of the log and/or the ID of the LOG related to the error that occurred and triggered the "Error handler"!  Current Behaviour - it does not exist.

We would like the Workfront Mobile App to allow the screen to be mobile-responsive and display all information in landscape mode.Some of our project names are long so it only displays some of first and last characters with an ellipsis in the middle when searching for projects.  We are hoping landscape mode would fix that issue and make the app more user friendly.  

Description - Please add the Workfront Project "securityAncestorsDisabled" field to the "Project Endpoint" in the public API!! It's shocking that this is not in the public api and part of the internal-only api. Why is this feature important to you - it would be good for us to have this type of information to better align data over fusion updates and also have the ability to better know which projects are intentionally isolated from permissions.  Going through the internal API is harder.  How would you like the feature to work - add the "securityAncestorsDisabled" field to the Project Endpoint in the "public api". Current Behaviour - the field "securityAncestorsDisabled" is only available in the private/internal-only api. Thank you,DD

Description - Do not allow time to be entered on a project or task before the Start Date (planned or actual) Why is this feature important to you - better compliance when it comes to entering time/timesheets and in the end give more accurate reporting. Currently our team is using Workfront for time/timesheets so it is important to be as accurate as possible.  How would you like the feature to work - When a user goes to enter time on a project or task, the days before the start date of the object are greyed out, not allowing them to enter time in the past or before the object was created. Helpful if this could be an option in the Setup menu.  Current Behavior - The user can enter time in the past for a project or task that was just created, giving inaccurate data on Timesheets and in reporting.