2020.2 Project enhancements

This page describes all Project enhancements made with the 2020.2 release to the Production environment. These enhancements were made available in the Production environment the week of May 11, 2020.

For a list of all changes available with the 2020.2 release, see 2020.2 release overview.

For Workfront administrators: New failsafe when the project status for new projects is hidden or unlocked

In Setup, you configure a preference to ensure that every new project has a certain status when the project is created. This is important because a project always needs a status in order to function properly in Workfront, even when the project is brand-new.

To make sure that new projects always have a status, even if an administrator hides or unlocks the status configured for new projects, the system now assigns the first status in the Status list to all new projects until you configure the new status for new projects once again.

For information about setting the preference for the status of all new projects, see Configure system-wide project preferences (or if you are using Adobe Workfront Classic, see Setting Project Preferences).

Available in these environments:

For Workfront administrators: Improved design in Project Preferences

The experience of setting project preferences is now more intuitive and easy to use:

For information about the Project Preferences area, see Configure system-wide project preferences (or if you are using Adobe Workfront Classic, see Setting Project Preferences).

Available in these environments:

Selected Filter, View, and Grouping retained in Report lists

Now, the last Filter, View, or Grouping applied to a specific report is selected, even if the user logs out and back in to Workfront.

Previously, after a user applied a Filter, View, or Grouping to a Report list and then navigated away from that page, the default Filter, View, or Grouping appeared the next time the user navigated to that same report.

Available in these environments:

Moving and copying tasks to another project keeps the task constraint when tasks can fit within the project’s timeline

We have made an improvement to the way Workfront handles the date-specific Task Constraint of a task when you copy the task or move it to another project. Examples of date-specific Task Constraints are Must Start on, Must Finish On, Fixed Dates, Start No Later Than, and so forth.

For example, when you move or copy a task with a Must Start On constraint to another project whose Planned Start Date is prior to the Start Date of the task, the task keeps the constraint after it is copied or moved. When you move or copy a task with a Must Start On constraint to a project whose Planned Start Date is after the Start Date of the task, the Task Constraint changes to As Soon As Possible.

Prior to this change, the Task Constraint always changes to As Soon As Possible.

For information about moving tasks see, Move tasks (or if you are using Adobe Workfront Classic, see Moving Tasks).

For information about copying tasks, see Copy and duplicate tasks (or if you are using Adobe Workfront Classic, see Copy and Duplicate Tasks).

For an overview of all Task Constraints, see Task Constraint overview (or if you are using Adobe Workfront Classic, see Task Constraint Overview).

Available in these environments:

Preventing data loss while making changes in the Details tab or a task list

To prevent data loss when you are updating information on the Details page on an object or tasks in a task list at the project level when saving changes manually, a warning message now displays, to notify you that you have unsaved changes before you attempt to edit information in the header. The only actions allowed before you save your changes are subscribing or adding the object to your favorites.

For information about editing tasks in a list, see Edit tasks in a list

Available in these environments: