How group and approval process changes affect assigned approval processes
This article explains what happens when an approval process is already associated with tasks, issues, projects, templates, or template tasks and a Workfront administrator (or a user with administrative access to approval processes) does one of the following:
- Changes the approval process (group-level) from one group to another
- Changes the group associated with the project
- Changes the approval process from group-level to system-level
- Changes the approval process from system-level to group-level
The article also describes what happens when moving or copying tasks or issues associated with a group-level approval process between two projects from different groups.
For information about the 3 types of approval processes you can use in Workfront, see Approval process overview.
Changing a group-specific approval process from one group to another
The following scenarios occur when a group-specific approval process is already being used on an object and someone reassigns it to a different group:
The Task Default Approval Process field is reset to N/A.
By default, no approval processes are associated with new tasks on the project.
The Default Approval field is reset to N/A.
By default, no approval processes are associated with new issues or requests on the project.
The Default Approval field is reset to N/A.
No approval processes are associated with new issues or requests on the project by default.
Changing the group associated with a project
When someone changes the group associated with a project to different group, the following occurs:
The Task Default Approval Process field is reset to N/A
By default, no approval processes are associated with new tasks on the project
The Default Approval Process field is reset to N/A
By default, no approval processes are associated with new issues or requests on the project
The Default Approval Process field is reset to N/A
By default, no approval processes are associated with new issues or requests on the project
Changing an approval process from group-level to system-level
When someone changes the Group option in a group-specific approval process to “All groups,” the approval process becomes system-wide and the following occurs:
Changing an approval process from system-level to group-level
When someone changes the availability of a system-wide approval process from “All groups” to a specific group, the approval process becomes group-specific and the following occurs:
Projects
Tasks
Issues
The Task Default Approval Process field is reset to N/A.
By default, no approval processes are associated with new tasks on the project.
The Default Approval field is reset to N/A.
By default, no approval processes are associated with new issues or requests on the project.
The Default Approval field is reset to N/A.
By default, no approval processes are associated with new issues or requests on the project.
Moving or copying a task or an issue to a project with a different group than that of the approval process
Moving or copying a task or an issue from a project to another might affect existing approval processes on the task or the issue depending on the groups of the two projects. The following table illustrates the scenarios that might exist: