A Resolvable Object is an issue whose resolution is tied to a Resolving Object. A Resolving Object is a project, task, or another issue.

When you convert an issue to a task or a project, the issue becomes the Resolvable Object of the task or the project. You can also manually link an issue to a Resolving Object, which can be a task, project, or issue.The original issue becomes the Resolvable Object of the task, project, or issue, in this scenario.

As a system administrator, you can decide how you want to handle the Resolvable Objects in your system.

You can select to keep the Resolvable Object as you are converting it to a task or a project, or to delete it once the task or project are created. You can select to allow these settings to be changed in the process of converting issues, which will allow the user converting the issues to select whether to keep or to delete the issue as they are converting it.

NOTE Resolvable Objects are always issues whose resolution and status can depend on the resolution and status of the Resolving Object they are associated with. Resolving Objects can be issues, tasks, or projects.

To establish the system default for what happens to the issue as it is being converted to a task or a project:

Log in to Workfront as a system administrator.

Navigate to Setup.

Expand Project Preferences.

Click Tasks & Issues.

Navigate to the Issues area of the setup. Consider editing any of the following settings:

Automatically update Resolvable Issue status when the status of the Resolving Object changes: Select this option to tie the resolution of the original issue to the resolution of its Resolving Object. In order for this setting to have any effect, the options to Keep the original issue and tie its resolution to the task or project must be selected.- When this setting is enabled, you can create custom statuses with the same key for both issues and projects or tasks. When the project or task (as a resolvable object) turns into the custom status, the change also reflects on the status of the issue. The status key must be the same for the issue and project or task statuses. - When this setting is disabled, resolving object statuses are automatically set to the default status, instead of the custom ones. For more information about the default statuses, see "Synchronizing the Status of the Resolving Object with that of the Resolvable Object."NOTE The default status of the issue is controlled by the status of the project or task, regardless of whether this option is selected or not.

When converting an issue to a TASK...: The settings in this section determine what happens during the conversion process from issue to task:

Keep the original issue and tie its resolution to the task: When converting the issue, it remains visible as an issue until the task is complete. The status of the issue automatically changes to Closed when the task completes.

Allow Primary Contact to have access to the task: Gives the primary contact (issue creator) access to the task to review the task, make updates, and stay informed of its progress.

Allow these settings to be changed during conversion: Allows the user who is converting the issue to change these options during the conversion of an issue to a task.

When converting an issue to a PROJECT...: The settings in this section determine what happens during the conversion process from issue to project:

Keep the original issue and tie its resolution to the project: When converting the issue, it remains visible as an issue until the project is complete. The status of the issue automatically changes to Closed when the project completes.

Allow Primary Contact to have access to the project: Gives the primary contact (issue creator) access to the project to review the project, make updates, and stay informed of its progress.

Allow these settings to be changed during conversion: Allows the user who is converting the issue to change these options during the conversion of an issue to a project.

Click Save.

Handling the Resolvable Object during the Conversion to a Project or a Task

If the system administrator has the Keep the original issue and tie its resolution to the task and the Keep the original issue and tie its resolution to the project selected and the Allow these settings to be changed during conversion unselected, you will not be able to change these settings as you are converting issues to tasks or projects.

If the system administrator has the Keep the original issue and tie its resolution to the task and the Keep the original issue and tie its resolution to the project either selected or unselected and the Allow these settings to be changed during conversion selected, you will be able to change these settings as you are converting issues to tasks or projects.

You can manually tie the resolution of an issue to the resolution of a project, task, or issue without converting the issue. The issue becomes one of the Resolvable Objects of the project, task, or issue you select. When you do this, a change in the status of the project, task, or issue triggers a change in the status of the original issue, so you cannot manually edit the status of the original issue. For more information about how the status of the Resolving Object affects the Resolvable Object, see "Synchronizing the Status of the Resolvable Object with that of the Resolving Object."

You must have Manage permissions on the original issue and View permissions on the project, task, or issue to do this.

To tie the resolution of an issue to the resolution of a project, task, or issue:

Navigate to an issue whose resolution you want to tie to a task or a project.

Select the Issue Details tab.

Click Edit Overview.

At the bottom of the form, in the Resolved By field, select from the following:

Project

Task

Issue

After selecting the object, start typing the name of a specific project, task, or issue and select it when it appears in the drop-down list.

Click Save. The original issue becomes the Resolvable Object for the project, task, or issue you selected in step 4 and 5. NOTE One project, task, or issue may have multiple issues as Resolvable Objects.

Synchronizing the Status of the Resolvable Object with that of the Resolving Object

If an issue is manually tied to another issue, the status of the second issue (Resolving Object) triggers a change in the status of the first issue (Resolvable Object). The status of the first issue matches the status that the second issue is changed to. This applies for both default and custom issue statuses.

Synchronizing Statuses when the Resolving Object is a Task or a Project

When an issue is the Resolvable Object of a task or a project, the changes in the status of the tasks and the projects trigger changes in the status of the issue. Default statuses are triggered differently than Custom statuses, in this case.

Synchronizing the Default Status of the Resolving Object with the Default Status of the Resolvable Object

Regardless of whether the Automatically set issue statuses to match the resolvable object using the Status keysoption is selected or not, every time the default status changes on the Resolving Objects (projects or tasks), the status of the Resolvable Object (issues) changes, accordingly. Only default statuses are already mapped to trigger such a change.

The following default statuses for tasks trigger the following changes in the default statuses for issues, when the issue is set as the resolving object of a task:

TASK STATUS

ISSUE STATUS

New

New

In Progress

In Progress

Complete

Closed

The following default statuses for projects trigger the following changes in the default statuses for issues, when the issue is set as a Resolvable Object of a project. Some project statuses do not trigger changes to the status of the issues. The issues remain in the status they were before the project was turned into one of these statuses:

PROJECT STATUS

ISSUE STATUS

Planning

New

Current

In Progress

On Hold

On Hold

Requested

Does not trigger a change to the issue status

Approved

Does not trigger a change to the issue status

Rejected

Does not trigger a change to the issue status

Idea

Does not trigger a change to the issue status

Dead

Closed

Completed

Closed

NOTE After the status of the issue becomes Closed, regardless of what status the task or project changes to, the issue remains Closed.

Synchronizing the Custom Status of the Resolving Object with the Custom Status of the Resolvable Object

When you change the status of the task or project to a custom status, the status of the issue changes to a custom issue status only if the following two conditions are met:

The custom status of the project or task has the same three letter code as the custom status of the issue.

You can create custom statuses with the same key for both issues and projects or tasks. When the project or task (as a Resolving Object) are changed to the custom status, the change also reflects on the status of the issue. The status key must be the same for the issue and project or task statuses.

For example, create a project custom status named "Launched" with the three letter code "LCD" which equates with "Current". Also, create an issue custom status named "Project Launched", also with the letter code "LCD" which equates with "In Progress". When you mark the project as "Launched", the issue will automatically change the status to "Project Launched". If the Automatically set issue statuses to match the resolvable object using the Status keys setting were not enabled, the issue status would change to "In Progress" instead (the default status). For more information about creating a custom status, see "Creating and Customizing Statuses for the Workfront Site."

Locating the Resolvable Object on a Task or a Project

Locating the resolving object is identical for tasks and projects.

Navigate to a project or a task which you created by converting an issue to the project or the task.

Select the Project Details or the Task Details tab.

At the bottom of the tab, locate to This Resolves field: the issue which is the Resolvable Object of the project or the task is listed in this field. NOTE Issues cannot be converted to other issues, but they can manually be associated with a Resolving Issue. A project, task, or issue can have multiple issues as Resolvable Objects. When the project, task, or issue resolves, the Resolvable Object (issue) also resolves. The Resolvable Issue remains closed even if the project, task, or issue that resolved it re-opens.

Identifying an Issue with a Resolving Object in a List

In a list of issues, you can identify issues that are labeled as resolving objects via status icons by locating this icon in the Status Icons or Flags columns:

Viewing Resolvable and Resolving Object Information in a Report

**^

You can display information about the Resolvable or Resolving Objects in the view or report for projects, tasks, or issues.The following table shows what fields you can display and in which views you can display them:

Field in View

Issue View

Task View

Project View

Has Resolvables: Displays a True value if the project or task has Resolvable Issues associated with them, and a False value if they do not.

✓

✓

✓

Original Issue Name, Original Issue Entry Date, Originator Name: Displays the name and entry date of the original issue, as well as the name of the user who created the issue in a text-mode customized view.For more information about building a text mode custom view for a project or task report or list to display information about the original issue, see "View: Display Original Issue Information on Task and Project List."

Thank you for taking the time to provide feedback. We appreciate and value your contribution to our site. Feedback provided here is regularly reviewed by our Product Documentation team. Please ensure your comments are specific to improving this help article. Any questions or requests outside this help article content should be directed to our Community User Forum or by submitting a ticket to customer support.