If groups in your organization need to configure a task or issue preference independently from the way it is configured at the system level, an Adobe Workfront administrator can unlock the preference. Then, as a group administrator, you can configure the preference for your group and it will affect all tasks or issues associated with your group.
If there are any groups above the group you manage, their administrators can also do this for your group. The same is true for Workfront administrators (for any group).
For information about how the Workfront administrator unlocks preferences, see Lock or unlock project preferences for all groups in the system.
Group-level configuration is also possible for project preferences. For information, see Configure project preferences for a group.
Typically, an unlocked preference remains unlocked indefinitely. If the Workfront administrator re-locks it, the system setting takes effect again and settings for the preference made by the group administrators are lost.
The preferences set for the group that is associated with a project take precedence over the preferences set for the Home Group of the user who creates the project.
Some group-level preferences affect project templates that you create for the group. For more information, see the section View, work with, and create templates for your group from the Groups area in the article Create and modify a group’s project templates.
After a Workfront administrator unlocks a preference at the system level, you can configure it and then lock it to ensure that everyone in your group and in its subgroups is using the same configuration. This is parallel to the ability that a Workfront administrator has to configure and lock a preference for everyone in the system. For more information, see Lock or unlock a project, task, or issue preference for subgroups.
You must have the following to perform the steps in this article:
|Adobe Workfront license*||
*If you need to find out what plan or license type you have, contact your Workfront administrator.
If you are a Workfront administrator, you can bypass steps 1-4 by going to Setup > Project Preferences > Tasks & Issues, then searching for the group’s name in the box at the top of the page.
Click the Main Menu icon in the upper-right corner of Adobe Workfront, then click Setup .
In the left panel, click Groups .
Click the name of the group for which you want to configure unlocked task and issue preferences.
On the page that displays for the group, in the left panel, click Task & Issue Preferences.
On the page that appears, continue with one of the 5 sections listed below these steps to configure settings for the areas New Task Defaults, Issues, Deletion, Actual Dates, and Access, then click Save.
If you hover over the lock icon for a preference that you need to configure and a tool tip displays to tell you that is locked, you can ask your Workfront administrator to unlock it for all groups in the organization.
When it is unlocked, you and other group administrators can configure it separately for your own groups. Also, you can lock it for your group and any subgroups below your group.
|Start Date on New Tasks||
Determines the default start date for new tasks for project managers. The start date for new tasks can either be the planned start date of the project or the day the task is created on.
Determines the relationship between the number of resources (and their allocation percent) and the duration or the total effort for the task. For more information, see Task Duration and Duration Types
Calculates planned and actual revenue estimates for a task. When the Revenue Type is set toNot Billable, the hours planned and the actual hours recorded do not generate a revenue estimate for the task, and the work on the task does not contribute to project-level revenue.
Calculates planned and actual cost estimates for a task. When set to No Cost, the hours planned and the actual hours recorded do not generate a planned or an actual cost estimate for the task, and the work on the task does not contribute to project-level costs.
|Automatically update Resolvable Issue status when the status of the Resolving Object changes||
When someone converts an issue into a project or task, both the original issue and the converted project or task become resolving objects. This setting lets you correlate the resolution of the original issue to the resolution of its resolvable object. For more information on resolving objects, see Overview of Resolving and Resolvable Objects .
In order for this setting to have any effect, the option to Keep the original issue and tie its resolution to the task must be selected.
|When converting an issue to a task||
The settings in this section determine what happens during the conversion process from issue to task:
|When converting an issue to a project||
The settings in this section determine what happens during the conversion process from issue to project:
|Allow users to delete tasks & issues with logged hours||
Lets you determine whether you allow the deletion of tasks or issues where hours are logged. This option is selected by default.
Tip: This setting also applies to deleting projects that have tasks or issues with hours logged on them. This setting does not apply to deleting projects where time is logged directly for the project.
Consider the following:
|When a task or issue goes from "New" to "In Progress," set the Actual Start Date to||
Select one of the following options for when the Actual Start Date is recorded in Workfront when a task or issue goes from New to In Progress:
|When a task or issue is completed, set the Actual Completion Date to||
Select one of the following options for when the Actual Completion Date is recorded in Workfront when a task or issue is completed:
|When someone is assigned to a task||
|When someone is assigned to an issue||
|When someone submits a request||