Converting JIRA sub-tasks to parent issues

Currently, the business owner has a series of parent issues that have large numbers of software defects logged as sub-tasks of these parent issues. Now that the software is out of development, they want these subtasks to follow the standard defect ticket flow. Is there any way to convert these sub-tasks to defects? Using the Move function only yields the option to change the sub-tasks to different types of sub-tasks. I can't actually make them independent parent tickets.

3 answers

1 accepted

18 votes
Accepted answer

Under options, there should be a "convert to issue" (Conversely, on parent types, you should see "convert to sub-task")

Can this be done in bulk, or only on an individual ticket basis?

Thank you Nic. I also would like to know if this bulk migration is possible since I will be doing the same thing this weekend. Thanks!

It's single issue at a time I'm afraid.

It is what it is I guess. Thanks again Nic. Feelsbadman.jpg

This option is not available for our Developers, although it is available to the Administrator. I cannot find a permission that grants a "Convert" action... Any ideas? (This is in Cloud 6.3).

Do your developers have "edit" rights on the issues?

Thanks this works.


What is super confusing is that if you try to EDIT a Subtask, it says this (see screenshot) next to the Issue Type. 

So you click on the "moving" link and then you can't move the issue to a different type, because it only allows you to move it to a different type of "sub-task" which makes no sense. Are there multiple types of sub-task? No, so it then says N/A next to that option. 


I think this message should be removed. Like most of Jira, the Ux is all over the place and finding where you need to go to do certain tasks takes a lot of Googling and not user-discoverable at all. 

Like 2 people like this

It does sort of make sense when you get the underlying structure, but if you were to say "it is worded really badly in the UI and counter-intuitive everywhere it is explained", I'd completely agree.

Maybe, but I am of the opinion that users shouldn't need to know the underlying structure, beyond high level workflow, in order to use a UI.

Oh I agree, definitely.  I was just saying that when you do have  knowledge, you can see how Jira ended up doing it this way.  But it's badly worded and presented to the users, forcing them to either learn the structure, or learn a clunky routine.

I see your point. I think the general problem is programming driven design. Perhaps business analyst driven design. Maybe it is the challenge of trying to find where to bolt on new features in what was originally well designed but has become cluttered. Its not easy.

The "convert to issue" is not showing up on my colleagues menu...I've looked everywhere to figure out why...she's also an system admin as am I. Why would this not be an option for her, when it is for me?

Like 1 person likes this

Do you have edit and create permission in the project?  (Admin rights are rightly separated from project permissions and irrelevant here)

So I was thinking the same thing...I thought it may be Project > Settings > People. But I gave her both Project Permissions of Project administrator and Developer (we are very small), however it still does not show up in the menu, even after refreshing and log out/in again.

So I've figured out that it's missing on the New Jira Issue View. Discovered when she went to Personal Settings and toggled OFF the New Jira Issue View, the "Convert to Issue" shows up with the same menu as mine. @Nic Brough [Adaptavist] Thank you for the help, and apologies for the multiple threads.

Like 2 people like this

Thank you, @Walt Harper


I switched to old view and I found it.

I voted for this because you CAN'T take these features away

Wow, thanks for the info that "convert to task" does not work in our default view.

I voted here:

Like 1 person likes this

Yes. I did not find a solution and advised my users to get their mouses clicking.


The bulk migration can be done following the below steps:

1. Prepare the CSV with only issue with Key, Summary and Issuetype fields.
2. Import the issue using CSV import. Please refer to the below link if you are not across:

3. You have to check the 'Map field value' field in 'Map fields' screen for the 'issue type' field.
4. Map the subtasks to the parent issue types.



Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

89 views 0 4
Read article

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