Convert a subtask to a story in Jira

Company-managed space

Company-managed spaces have a dedicated conversion flow. The target work type must be available in the space's work type scheme, and required fields for the new type must be filled before Jira can finish.

1. Open the subtask

   Open the subtask itself, not its parent, then select More actions (•••) → Convert to work item.

2. Choose Story or another standalone type

   Select the target type, such as Story, then choose Next. If Story is absent, an admin needs to add it to the space's work type scheme.

3. Map the status when Jira asks

   If the subtask's current status is not allowed by the Story workflow, choose a valid new status. This is why a simple type change sometimes turns into a move-style wizard.

4. Fill the target type's required fields

   Jira carries compatible values across, then asks for anything required by the Story screen or workflow. Set those values and select Next.

5. Review and finish

   Review the mapping and select Finish. The converted work item is now standalone; its former parent is no longer set.

Team-managed space

Team-managed spaces use the general Move flow for the same conversion. Their child-work-item model is simpler, but changing type can still expose fields that only exist on the target type.

1. Open the child work item

   Open the item you want to promote and select More actions (•••) → Move.

2. Change the work type

   In the move table, choose Story (or the standalone type you need) from the work type dropdown, then select Next.

3. Complete any required fields

   Enter values Jira requests for the new type. Leave Send mail for this update unchecked unless the conversion warrants a notification.

4. Confirm and acknowledge

   Review the change, select Confirm, then Acknowledge. The item no longer has the parent relationship it had as a child work item.

Good to know

Type changes expose configuration differences that ordinary editing hides:

• Status and workflow must match. Jira asks for a new status only when the old one is not valid for the target type.
• Required fields can block the conversion. Add values for the target type rather than cancelling and trying the same move again.
• You cannot turn a parent with children straight into a subtask. Convert its children to standalone work items first.
• Moving a subtask to another parent is two conversions. Convert it to standalone, then convert it back to a subtask or child under the new parent.