Access the list of system issue statuses
You can use the status of an issue to show users in the system in what stage of development an issue is at a given time.
Access requirements
You must have the following access to perform the steps in this article:
| table 0-row-2 1-row-0 2-row-2 3-row-2 layout-auto html-authored no-header | |
|---|---|
| Adobe Workfront plan | Any |
| Adobe Workfront license |
New: Standard Or Current: Plan |
| Access level configurations | System Administrator |
For more detail about the information in this table, see Access requirements in Workfront documentation.
Access issue statuses
You can access and modify system-level issue statuses. You can edit some information about the default system statuses or you can create new custom statuses. For more information about creating custom statuses or editing system statuses, see Create or edit a status.
To access system-level issue statuses:
-
Click the Main Menu icon
-
Click Project Preferences > Statuses.
-
Click the Issues tab to see the issue statuses available in Workfront.
System issue statuses
Workfront comes with 10 original issue statuses. The first 4 in the table below are required, which means that you can unlock, rename, and reorder them, but you cannot hide or delete them.
You can add custom issue statuses to match the needs in your organization. For more information, see Create or edit a status.
For users, changing the status of an issue is typically a manual process. However, there are situations, outlined in the following list, when the status of an issue changes automatically, depending on other factors that are happening in the system.
The following issue statuses are provided with your Workfront instance:
You may place an issue in this status to indicate that work on that issue has started.
If the resolution of the issue is connected to another object (a task, project, or another issue), the issue status is changed to In Progress automatically, when you change the status of the resolving object to In Progress.
For more information about resolving objects, see Overview of Resolving and Resolvable Objects.
If the issue is on a project in a status of Current, the issue displays in the Working On tab of the users who are assigned to the issue.
When an issue is In Progress, the issue shows a value for the Actual Start Date.
You can manually mark an issue as Closed when the work on it is completed.
If the resolution of the issue is connected to another object (a task, project, or another issue), the issue status is changed to Closed automatically, when you change the status of the resolving object to Closed.
For more information about resolving objects, see Overview of Resolving and Resolvable Objects.
When an issue is Closed, the issue is removed from the assignee's Working On list. In this case, the issue shows a value for the Actual Completion Date.
When all the tasks are completed and issues are closed on a project, the project can be completed.
If the issue is on a project in a status of Current, the issue displays in the Working On tab of the users who are assigned to the issue.
When all the tasks are completed on a project, but there is at least one On Hold issue on the project, the project cannot be completed.
If the issue is on a project in a status of Current, the issue displays in the Work Requests tab of the users who are assigned to the issue. Users can now start working on the issue.
This status is important in reporting, to differentiate between issues that are open for the first time (usually in the New status), and issues that are opened after having been closed before (usually in the Reopened status).
If the issue is on a project in a status of Current, the issue displays in the Working On tab of the users who are assigned to the issue.
If an issue is Awaiting Feedback, a project cannot be completed.
This status is important in reporting, to differentiate between issues that are currently open but being worked on (usually in the In Progress status) and issues that are currently open but not being worked on because more feedback is needed to complete them (usually in the Awaiting Feedback status).
This status is important in reporting, to differentiate between issues that are completed and whose problem has been addressed (usually in the Closed status) and issues whose problem is not visible at a given time (usually in the Cannot Duplicate status).
When an issue is marked as Cannot Duplicate, the issue is removed from the assignee's Working On list. In this case, the issue shows a value for the Actual CompletionDate.
If all the tasks on a project are completed, and some issues are in a Cannot Duplicate status, the project can be completed.
This status is important in reporting, to differentiate between issues that are closed with or without a resolution (usually in the Closed status) and issues that are closed with an actual resolution (usually in the status of Resolved).
When an issue is marked as Resolved, the issue is removed from the assignee's Working On list. In this case, the issue shows a value for the Actual Completion Date.
If all the tasks on a project are completed, and at least one issue is in a Resolved status, the project can be completed.
When an issue is marked as Verified Complete, the issue is removed from the assignee's Working On list. In this case, the issue shows a value for the Actual Completion Date.
If all the tasks on a project are completed, and some issues are in a Verified Complete status, the project can be completed.
This status is important in reporting, to differentiate between issues that are closed with or without a resolution (usually in the Closed status) and issues that are closed without an actual resolution (usually in the status of Won't Resolve).
When an issue is marked as Won't Resolve, the issue is removed from the assignee's Working On list. In this case, the issue shows a value for the Actual Completion Date.
If all the tasks on a project are completed, and at least one issue is in a Won't Resolve status, the project can be completed.
Customizing issue statuses
A Workfront administrator can add system-level and group-level issue statuses to Workfront and change the order in which users see them. For more information, see Create or edit a status.
A group administrator can add a custom status specific to one group. For more information, see Create or edit a group status.