JIRA - Convert Subtask to Issue

Jira - Converting a Sub-task to a Standard Issue

In Jira, sub-tasks are issues that are created as children of a parent issue, helping to break down larger pieces of work. However, there are situations where a sub-task might outgrow its role or need to be managed independently. In such cases, Jira allows you to convert a sub-task into a standard, standalone issue.

To convert a sub-task to a standard issue:

1. Navigate to the Sub-task: Open the specific sub-task that you intend to convert.
2. Access Conversion Option: On the sub-task’s view screen, look for an actions menu (often represented by ’…’ or labeled ‘More’). Within this menu, you should find an option like ‘Convert to Issue’. Select it to begin the conversion wizard.

The conversion process typically guides you through a few steps:

Step 1: Select New Issue Type

You will be prompted to choose the new, standard issue type for the item once it’s converted (e.g., Task, Story, Bug). Select the desired issue type from the provided dropdown list that best fits the nature of the work. Click ‘Next’ (or an equivalent button) to proceed.

Step 2: Select New Status (If Applicable)

If the sub-task’s current status (e.g., ‘In Progress’) is not a valid status for the new standard issue type you selected in Step 1, Jira will require you to choose a new, valid status for the converted issue from a list of available statuses for that issue type. Select an appropriate status and continue.

Step 3: Update Fields (If Applicable)

The new standard issue type might have different field requirements or layouts than the sub-task. Jira may prompt you to update certain fields, confirm existing field values, or populate new mandatory fields that weren’t present on the sub-task. In some cases, a message like ‘All fields will be updated automatically’ might appear if no manual intervention is needed. Review any prompts and make necessary changes before proceeding.

Step 4: Confirmation

A confirmation screen will often display a summary of the changes, showing the original sub-task values and the proposed new values for the converted issue. Carefully review this information. If everything is correct, click ‘Finish’ or ‘Convert’ to finalize the conversion.

Once converted, the item is now a standard, independent issue. It will no longer be hierarchically linked as a sub-task to its former parent issue. The reference to the parent issue (often displayed at the top of a sub-task’s screen) will be removed. The new issue will have its own lifecycle and can be managed like any other standard issue in the project.

When to Convert a Sub-task to an Issue

Consider converting a sub-task if:

• Scope Creep: The sub-task has grown significantly in complexity or effort, becoming substantial enough to be managed as a standalone piece of work.
• Independent Prioritization: The work item, initially part of a larger task, now needs to be prioritized, scheduled, or tracked independently of its original parent.
• Different Workflow/Context: The sub-task requires a different workflow, different custom fields, or needs to be moved to a different project where it makes more sense as a standard issue.
• Reporting Needs: You need to report on this piece of work separately, and its status as a sub-task is limiting your reporting capabilities.

Important Considerations

• Loss of Direct Parent Link: Converting a sub-task to a standard issue permanently severs its direct, hierarchical sub-task link to the original parent issue. If you still need to maintain a contextual relationship, you can manually link the newly converted issue back to the original parent using standard issue linking features (e.g., with a ‘relates to’ link type).
• Permissions: You must have the necessary project permissions to convert sub-tasks to issues. These permissions (often related to ‘Edit Issues’, ‘Move Issues’, and specific conversion permissions) are managed by your Jira administrator. If you don’t see the option, you may lack the required permissions.