How do you re-assign a subtask to a different story?

Keeping the same sub-tasks, need to create new story for the subtask to live under w/o deleting and re-creating the story.

3 answers

1 accepted

Accepted Answer
14 votes

Hi Bruce,

You can simply "move" the sub-tasks to a new parent/Story. In each of the sub-tasks, go to more actions > move, then select change parent.

Hope it helps,

Hi, thank you. I looked at what I was dealing with and the item is listed as a task and not a subtask, so I'll rephrase my question: How does one turn a task into a subtask and assign a parent task?

Bruce, that's really simple. Create the parent first (if you don't have it yet), then open the task, click on more actions > convert to sub-task. You'll be prompet to a screen where you'll be able to select the parent for that subtask, and it's done. :)

There is no ""move" menu in my Jira, and therefore no "change parent".


What permission is required, or... if the methodology has changed, how is it done now (Septemeber, 2017)?

Same here as Wayne Erfling. Has this feature been removed?

Hi !

I try to move a sub-task to another parent, but an error occurs:
"Subtasks cannot be moved".

It is a configuration? Any help ... 

Thanks

Do you have create, move and edit permission in both the source and target projects?  (I say "Projects" to cover the assumption that you're trying to move from one project to another with this move)

Hi Nic,

I trying to perform this in same project, just from an issue to another.

I think you'll need to read the log file for the time you get the message.

Hi all,

I found an alternative.

1. Select the sub-task and choose 'Convert to issue'

2. Select the category 'Unclassified' while converting

3. Now the item is independent and you can convert to sub-task and map whichever story you want.

Hope this help.

I am voting up this although it is not straight fwd - i wish Atlassian doesnt change some fundamental features. Well found Rakesh and thanks!

None of the above solutions seems to work for me - There is no ""move" menu in my Jira.

You don't need "move", you need "convert to issue".  Atlassian are unlikely to change anything here, because it's working fine.

Rakesh's mention of "unclassified" is irrelevant, it's just something in that particular Jira that probably isn't in yours.

I agree "unclassified" is not necessary.

From earlier comments I understand there was a "Move" and you just had to choose new parent (dated 2013, with 10+ votes).

A one step "convert to issue" is not sufficient, will have an additional step to "convert to subtask".

You don't have to convert to an issue and then back to a sub-task to change the parent.

When you use "move" on a sub-task, it will ask you if you want to change the issue type or the parent issue. 

I want to do this as well. I created tasks first and want to assign to a parent. However I dont see "convert to sub-task" under more actions. Is that configurable or something?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

27,466 views 2 7
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