how to convert subtask to story

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

how to convert subtask to story?

5 answers

hi, 

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". 

cheers,

damien.

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

image.png

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

image.png

image.png

Like 1 person likes 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!

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

Like 2 people like this

Hi matilda majed,

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

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 2 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 3 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 1 person 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

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 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 ...

372 views 6 0
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you