This question is in reference to Atlassian Documentation: JIRA User's Guide
how to convert subtask to story?
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.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But soon everybody will be on the New View, how can we convert subtasks to issues after that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Kindly fix this so the 2019 view can be used to achieve this. This is not a minor oversight by any generous measure!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
3rd thread here I had to look at to get this working. Thx
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks . Didn't know the existance of such option!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi matilda majed,
Sub-task issue -->view issue screen see more options ---> select convert to issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you click the icon next to the ticket number you will find a dropdown menu where you can select the correct type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
productivity is reduced by constant design framework changes, and then not implementing features in the new design. This keeps happening with Atlassian.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just pres dot "." and type "issue", in new version you can convert it right away!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I cannot find "convert sub-task to issue" only change parent..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Or maybe need to use "Move Issue" instead of "Edit Issue" in bulk change wizard?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There will be a "convert sub-task to issue" option in the tools menu on the issue view (along with log work, attach, etc)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.