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

Moving sub-tasks to new parent with Bulk Update

I am not able to move sub-tasks to new parent with Bulk Update functionality. How can this easily be accomplished without going to each individual sub-task and selecting "Move"

4 answers

1 accepted

I realize this has already been answered, but if you want to do this with native JIRA rather than a plugin, you can do it in two steps:

  1. Bulk Move your subtasks to any parent Issue Type in the same project
  2. Bulk Move these parent Issues back to Subtasks, you will be prompted for the new parent

 

Hi Eric,

I tried to follow these steps but I was only given other sub-task issue types to choose as my new issue type.  If you found a way around that can you share?

Thank you

Strange. I am sorry; I have not seen this behaviour so I am not sure what would be causing it. When I go to Bulk Move any subtask issue type, all of my normal issue types are available for selection as well.

Thanks for the quick response.  I will play with it and see if it's a setting in our admin I can change.  We are using JIRA Server v6.2.

For Jira Cloud:

1. Open the parent item to display the linked subtasks and decide which parent issue key you want to move the subtasks to.

2. Copy the issuekey numerical portion (trn-113) as 113 for all subtasks to be moved.

3. Figure out what the project 'prefix' is (the acronym for the project name that appears in front of all issue id's for your project: If 'TRAIN' is project then 'trn' may be the prefix. (you chose this when you created the project).

3. Click the search tool (magnifying glass in upper left of 'management column area?'.

4. Don't enter anything on the search entry field.

5. Click the 'Advanced Search' magnifying glass.

6. type (without quotes) into search field: issuekey in ()

7. past in all the issue key numerical portions you copied: 113, 114, 156 ,199, 333356, etc. between the parens: "issuekey in (113, 114, 156 ,199, 333356)".

8. repetitively insert the project 'prefix' and comma+space delimiter : ', trn-' between each numerical key portion; issuekey in (trn-113, trn-114, etc...)

9. select 'bulk change' in upper right of search screen.

10 proceed as usual with 'bulk change'. 

11. choose all issues in 'next' screen, click 'next'.

12. choose 'move' in 'change operation screen', click 'next'.

13. (a) choose project to move to (not), (b) issue type to change to (NOT), (c) parent issue to attach to.

14. check checkbox titled: 'Use the above project and issue type pair for all other combinations.'

15. Click next: all subtasks will be attached to the issue you selected in #13. step (c) above.

16. Wonder what else you may accomplish using this method.

Suggest an answer

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

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

302 views 1 3
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