Edit issues

This is a visual flag for you which allows you to prioritize issues.

Select from the following options:

• None

• Low

• Normal

• High

• Urgent

Depending on the Project Preferences selected by your Workfront administrator, the names of priorities might be different for you. For more information about editing priorities, see Create and customize priorities.

This is a visual flag for you which indicates how severe the problem described in the issue is. Severities are specific to issues. Select from the following options:

• Cosmetic

• Causes Confusion

• Bug with workaround

• Bug with no workaround

• Fatal error

Depending on the Project Preferences selected by your Workfront administrator, the names of severities might be different for you. For more information about editing severities, see Create or customize issue severities.

According to the Queue Properties selected by your project manager in the Queue Details area of the project, you might be able to specify the type of the issue. Select from the following options in the Type drop-down menu:

• Bug Report

• Change Order

• Issue

• Request

Depending on the Project Preferences selected by your Workfront administrator, the names of the types of the issues might be different for you.

By default, the Primary Contact is the creator of the issue. To modify this, start typing the name of any active user in Workfront, then select it from the list. An issue can have only one Primary Contact.
If you change the Primary Contact, the original primary contact still has Manage access to the issue. You must manually remove this access from the Issue Access box, when sharing an issue.

TIP

When adding a Primary Contact user, notice the avatar, the user's Primary Role, and their email address to distinguish between users with identical names. Users must be associated with at least one job role to view it as you add them.

You must have the View Contact Info setting enabled in your access level for Users to view users' emails. For information, see Grant access to users.

This shows whether the issue is resolved by another object. You can select whether this issue is resolved by a task, a project, or another issue from the drop-down menu, then start typing the name of the task, project, or issue that will resolve the issue. Select it when it appears in the list.

NOTE

When you select an object to resolve an issue, the issue status is linked to the status of the resolving object and cannot be changed on the issue. For more information about resolving objects, see Overview of Resolving and Resolvable Objects.

TIP

When your system or group administrator adds the “Resolved By” field to an issue custom header, the field changes to “Resolving Issue”, “Resolving Task”, or “Resolving Project” when there is a resolving object associated with the issue.

You cannot edit this field when it displays in the issue header. For more information about customizing issue headers, see Customize object headers using a layout template

• Reassign the work item to active resources.
• Associate the users in a deactivated team with an active team and reassign the work item to the active team.

This is the amount of actual time it would take the assignees of the issue to complete it. Type the number of Planned Hours for the issue.

Note: Changing the Planned Hours of the issue will not change the issue Planned Completion Date.

Select a role from the Assignee's Role drop-down menu when you selected a person as an assignee. This is the role that the assignee can fulfill on this issue.

TIP

Only the job roles associated with each assignee in their profile appear in the drop-down menu.

Select an approval process that you want to associate with the issue. Your Workfront administrator must define system-level Approval Processes before you can associate them with issues. Users with administrative access to Approval processes can also create group-specific approval processes.For more information about creating Approval Processes, see Create an approval process for work items.

Consider the following when adding approval processes:

• Only active approval processes display in the list.

• System-wide and group-specific approval processes display in the list. An approval process associated with a group other than that of the project does not display in the list.

  Important: If the group of the project changes, the group-specific approval process becomes a single-use approval process. For more information about how changes to the group of the project or changes in the approval process affect approval settings, see How group and approval process changes affect assigned approval processes.

• You can define default approval processes to be automatically attached to issues when creating request queues or Queue Topics. For information about updating Queue Details, see Create a Request Queue. For information about creating Queue Topics, see Create Queue Topics.

• When bulk-editing issues, the following scenarios exist:

  • When you select multiple issues from the same group, both system-level and group-specific approval processes display in this field.

  • When you select multiple issues from different groups, only system-level approval processes display in this field.

  • When any of the issues have a single-use approval process attached, it is replaced by the system-level or group-level approval process you select.