Overview of converting issues in Adobe Workfront

Last update: December 20, 2024

Topics:
Work Management

CREATED FOR:

User

If more work needs to be done to complete an issue after the issue is submitted, you can convert the issue to a project or to a task.

For information about converting issues to tasks, see Convert an issue to a task in Adobe Workfront.

For information about converting issues to projects, see Convert an issue to a project in Adobe Workfront.

Considerations when converting issues

When converting issues to tasks or projects, most information from the issue transfers to the task or project, unless otherwise specified in this article.
Your Workfront administrator or group administrator has already set the preferences for what happens to an issue, its resolution, and the its Primary Contact’s access when it is converted to a project or a task, as outlined in Configure system-wide task and issue preferences.
Workfront removes any approvals that are associated with issues during conversion.
Workfront overwrites the Resolving Object of the issue when you convert it to a task or an project. The new task or issue becomes the new Resolving Object of the issue after conversion.
Consider the following:
- During conversion, you might be asked whether you want to keep the issue and its resolution tied to the project or task you are creating.
- If you keep the issue, the status and percent complete of the project or task automatically update the status and the percent complete of the issue when any changes occur on the project, task, or the issue or when the Workfront recalculates the timeline.
NOTE
After the status of the issue becomes Closed (as a result of closing the task or the project), regardless of what status the task or project changes to after closing them, the issue remains Closed.
When converting an issue to a task or a project, the issue is removed from the Home area of the user assigned to the issue.
When converting an issue, the permissions to the original issues are not transferred to the converted object (task or project).
When converting an issue to a project using a template, most information from the template transfers to the new project. However, some information from the issue can also transfer to the new project. For more information, see the Overview of project fields when converting an issue to a project using a template section in this article.
While converting an issue, not all documents or their information are moved to the new object that the issue is converted to. The following items are included when you convert an issue that has documents or document links attached:
- Document
- Document links to third-party services, such as Google Drive or SharePoint.
- Versions
- Proofs are included only when the option Keep the original issue and tie its resolution to this task is unselected.
- Document approvals are not included when you convert an issue that has documents and document links attached.
If you decided to keep the issue in the conversion and it has documents attached, the document and its versions are copied to the project or the task. The proofs and the document approvals are not copied to the project or the task.
If you decided to not keep the issue in the conversion, and it has documents attached, the document, its versions, and the proofs transfer to the project or the task. The document approvals will not transfer to the project or the task.
If you have documents and folders linked to the original issue from third party services, like Google Drive, regardless of whether you are keeping the issue or not during the conversion, those links will be copied to the new object.
Issue comments are also copied to the task or project converted from the issue, but tagged users will not transfer.
If you want to transfer custom form information from the issue to the project or task you are converting it to, ensure you have a project or task custom form that include the same fields you want to transfer from the issue. For more information, see Transfer custom form data when converting an object.

Overview of project fields when converting an issue to a project using a template

When converting an issue to a project, you can either convert it to a blank project or use a template.

For information, see Convert an issue to a project in Adobe Workfront.

When using a template, some fields that are populated on the template transfer to the project created from the converted issue. Other fields transfer to the project from the converted issue.

The following table lists project information and whether it transfers from the template or from the issue:

Description	The Description of the issue transfers to the new project. If there is no description on the issue, the Description from the template transfers to the project. If the Description field is empty both for the issue and for the template, the field is empty on the project.
Status	Default status selected for the group on the template. If the template is not associated with the group, the project status is set to the default status set by the Workfront administrator in the Project Preferences area of Setup. For information, see Configure system-wide project preferences.
Priority	Transfers from the issue. When you use a template for the converted project, you have the option to manually change the Priority. If you choose not to change it, the priority of the issue transfers to the project.
URL	The URL from the issue transfers to the new project. If there is no URL specified on the issue, the URL from the template transfers to the project. If the URL field is empty both for the issue and for the template, the field is empty on the project.
Project Condition Type	Transfers from the template.
Project Condition	Matches the system-level default preference as determined by the Workfront administrator in the Setup area. For information, see Set a custom condition as the default for projects
Schedule From	Transfers from the template.
Project dates	Planned Start Date: The closest working time based on the template schedule's working time should be preselected, according to the timezone of the template's schedule. This field is disabled if the Schedule From field is set to From Completion. Planned Completion Date: The closest working time based on the template schedule's working time should be preselected, according to the timezone of the template's schedule. This field is disabled if the Schedule From field is set to From Start.
Portfolio	Transfers from the template. Otherwise, this field is empty.
Program	Transfers from the template. Otherwise, this field is empty.
Group	The following scenarios exist: If a group is specified during the conversion, that becomes the group of the project If you convert to a project using a template, and there is a group on the template, and during the conversion you do not specify a group, then the group of the template becomes the group of the new project If there is no group on the template and you do not specify a group during the conversion, then the group of the original issue's project becomes the group of the new project
Company	Transfers from the template. Otherwise, this field is empty.
Project Owner	Transfers from the Template Owner field on the template. Otherwise, it is set to the logged-in user who is performing the conversion.
Project Sponsor	Transfers from the Template Sponsor field on the template. Otherwise, this field is empty.
Resource Manager	Transfers from the template. Otherwise, this field is empty.
Task Settings	Transfer from the template.
Issue Settings	Transfer from the template.
Access	Transfers from the Access section on the template.
Approvals	Transfer from the template. The approvals associated with the issue are removed during the conversion.

View original issue information on projects and tasks

You can view the original issue information in project and task lists and reports or in the Project Details area. For information about building reports, see Create a custom report.

The following table illustrates which issue fields are visible from the converted projects and tasks.

Issue fields	Project or task field	Project list or report	Project Details area	Task list or report	Task Details area
Issue Name	Converted Issue Name	✔	✔	✔	✔
Primary Contact	Converted Issue Originator Name	✔	`✔`	✔
Entry Date	Converted Issue Entry Date	✔		✔

CAUTION

If the Primary Contact of an issue changes or if the issue becomes unlinked from the project or task after the issue has been converted, the Converted Issue Originator Name does not update and it displays the original Primary Contact of the issue at the time the issue was converted.

recommendation-more-help