It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

how to convert subtask to story

This question is in reference to Atlassian Documentation: JIRA User's Guide

how to convert subtask to story?

9 answers


simply move your issue to the same project but choose the story issue type. 

moving your issue can be done thanks to the 3 dots on the top right corner of your issue view and choose "Move". 



Tried Move - get a message:
"There are no other sub-task issue types associated with this project."


Turns out you have to switch to the Old View to see the option to "Convert to Issue".



Like # people like this

Thank you so much Bill! Saved my life! Is this new or we've just been blind? I guess I was always going to MOVE so maybe i missed it. Makes a world of a difference, thanks!

Like Phillip Terry likes this

But soon everybody will be on the New View, how can we convert subtasks to issues after that?

Like # people like this

Kindly fix this so the 2019 view can be used to achieve this. This is not a minor oversight by any generous measure!

Like # people like this

3rd thread here I had to look at to get this working. Thx

Its added to the new issue layout now..


Like R__Schreurs likes this

Thanks . Didn't know the existance of such option!

Hi matilda majed,

Sub-task issue -->view issue screen see more  options ---> select convert to issue.

productivity is reduced by constant design framework changes, and then not implementing features in the new design. This keeps happening with Atlassian. 

1 vote

If you click the icon next to the ticket number you will find a dropdown menu where you can select the correct type.

Screen Shot 2020-05-07 at 8.07.48 PM.png

0 votes

There will be a "convert sub-task to issue" option in the tools menu on the issue view (along with log work, attach, etc)

I cannot find "convert sub-task to issue" only change parent..


Do you have "create issue" rights in that project?

If you do, and you still don't have the option to convert sub-tasks to issues, then you'll need to ask your administrators to revert whatever it is they have done to remove it.

Or maybe need to use "Move Issue" instead of "Edit Issue" in bulk change wizard?

There's a problem with the new Issue View that Atlassian released a little while back. You just have to switch back to the classic issue-view and you should see it in the "More Actions" menu.

Like # people like this

Thanks to @Joshua McManus for that answer; that's the solution. Bulk edit didn't work. Checking permissions didn't work. They literally broke "Change Issue Type" in the new JIRA.


But we're used to things being broken with JIRA, so it's okay, right?

Like # people like this

This new view is an absolute disaster, why take a good product and mangle it beyond recognition! It has so many issues, I am dreading the time when they'll remove the old view! 

Like Katja Angerstein likes this

This is sort pain in the ASS.


Why not have Project - Project Version - Epic - Story - Task - Sub-task. I suppose this is the SCRUM structure. Atlassian made it this way in the previous version, but the new version seems to stupid. Who's the their new business analyst? 

Scrum is Epic -> Story -> (sub)task.  Jira is unlikely to change away from that, as that structure has been fundamental almost since it was first written.

So you're saying Story represents Task sort of? But it would be great if there is Task for Story and Sub-task for Task. With this structure more details can be captured.

Thanks anyway.

No, a task is an issue type that you could have at the same level as a story or below as a sub-task level.  Or not at all if you choose not to have tasks.

Any issue at the story level can have sub-tasks of any type you define.

Thanks for your explanation Nic

Just pres dot "." and type "issue", in new version you can convert it right away!

If you go to "all issues" view, and you filter what you want to change, there is an option now on the top right "..." menu that says "bulk change" (which of course you can use for a single issue as well).

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

3,024 views 11 5
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you