Can a subtask be converted, moved or otherwise turned into a parent task? Particularly…
- User
Can a subtask be converted, moved or otherwise turned into a parent task? Particularly if transitioning into a new project?
- Assistant
Yes — in Jira you can “promote” a Sub-task to a regular (parent-level) issue and, once it is a regular issue, you can move it to any project you like.
Below is everything you need to know:
Quick-fire summary
- You cannot move a Sub-task to another project while it is still a Sub-task (a parent and its Sub-tasks must live in the same project).
- First convert / promote the Sub-task to a standard issue type (Task, Story, Bug, etc.).
- Then move that new issue to the target project (or even convert it again to a different issue type such as Epic if you need).
Step-by-step (Jira Cloud & Data Center)
A. Promote the Sub-task to a regular issue
- Open the Sub-task.
- Click the ••• (“More” / “Actions”) menu.
- Choose either
• Convert to Issue (Cloud) ‑or-
• Move (Server/Data Center) and on Step 2 select a “standard” issue type. - Pick the new issue type (Story, Task, Bug, …) and click Next / Confirm.
• Jira detaches the item from its parent; it is now a top-level issue in that same project.
B. Move the new issue to another project (if required)
- Still on the issue, click ••• > Move.
- Select the destination project and the target issue type.
- Walk through the Move wizard: map any fields, set a status, fill mandatory fields.
- Finish → the issue jumps to the new project as a parent-level issue.
Permissions you’ll need • Move Issues permission in the source project.
• Create Issues permission in the destination project.
Edge cases & tips • If the destination workflow doesn’t contain the current status, Jira will ask you to pick a valid one.
• If you want to keep a trace of the original parent / child relationship, simply add an issue link (e.g. “relates to” or “is blocked by”) after the conversion.
• You can automate this with Jira Automation (rule trigger = “Issue transitioned” or “Issue created”, then action = “Edit issue » Change issue type” + “Move issue”).
• You cannot convert a Sub-task directly to an Epic in one step; promote to a standard issue first, then (if needed) convert that issue to an Epic.That’s it! Promote first, move second, and your Sub-task is now a full-fledged parent issue wherever you need it.
- User
Are workflows in Jira more inherently connected to an Issue Type or a Project?
- Assistant
Short version
A workflow is not “owned” by either an Issue Type or a Project.
Instead, Jira does this:- Create a workflow (global object).
- Put that workflow inside a Workflow Scheme, telling Jira “For Issue Type X use Workflow A, for Issue Type Y use Workflow B …”.
- Assign that Workflow Scheme to a Project.
So the marriage looks like this:
Project ──────► Workflow Scheme ──────► (Issue Type ▸ Workflow)Therefore …
• From the Issue-Type angle – an issue type only gets a workflow when it lives inside a project that has a workflow scheme.
• From the Project angle – a project decides which workflows it will use by the scheme it is given.Practical implications
Question Answer Can the same workflow be reused in many projects? Yes. One workflow can sit in multiple workflow schemes. Can the same issue type use different workflows in different projects? Yes. Because each project may map that issue type to a different workflow in its own scheme. Can a project have several workflows? Yes, one per issue type (or you can share one for all). Take-away
Think of workflows as “global templates.”
They become “the project’s workflow for an issue type” only after a workflow scheme glues the three pieces (project ⇄ issue type ⇄ workflow) together.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.