Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Move Epic WITH tasks together

Patrick Ferraro February 10, 2020

When I move an Epic to another project, the Epic goes fine, but the tasks of it don´t.

I can go to the "orfans" tasks and move them to the another project.

Is there a way to do all of this in one operation? Like Move Epic and all go with it?

 

1 answer

0 votes
Tony Rossiter
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 10, 2020

@Patrick Ferraro 

You can move them all together using the bulk change feature: 

  1. You need to have the Bulk Change global permission
  2. Go to the issues search and write a JQL query along the lines of key = [epic ticket key] AND epiclink = [epic ticket key]
  3. Bulk change all tickets returned in the search and move them to the new project

That should achieve what you're looking to do.  

https://support.atlassian.com/jira-core-cloud/docs/edit-multiple-issues-at-the-same-time/

Patrick Ferraro February 10, 2020

Tony, how can I get Epic Ticket Key ?

Patrick Ferraro February 10, 2020

Tony,

JQL I used (issueKey = "BPOOL-161") that returns my epic, but when I move it, just the Epic goes, the tasks remains.

Jack Brickey
Community Champion
February 10, 2020

is the workflow the same for the two (Epic and tasks)?

  1. if you are having issue then simply add a label to all of the tasks under the epic
  2. move the epic
  3. jql the issues by label
  4. bulk move the issues and be sure to set the epic link
Tony Rossiter
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 10, 2020

@Patrick Ferraro 

Don’t leave off the last part of that query:

key = [epic ticket key] AND "Epic Link" = [epic ticket key]

The clause after the AND is what brings in all of the other issues linked to the epic.  If you are trying to move actual sub tasks of the epic, change to:

 

key = [epic ticket key] AND parent = [epic ticket key]

Patrick Ferraro February 10, 2020

Jack, the point is that we are in 2020 and the jira Cloud supose to be "Easy"...

A simple move I have to do 5 operations?

Its not possible that Jira doesn´t make this easy as simple move w/ anything related...

Patrick Ferraro February 10, 2020

@Tony Rossiter 

the key = "BPOOL-161" AND parent = "BPOOL-161" doesn´t work (brings nothing)

key = "BPOOL-161" this brings the epic. But when I move it, just the Epic goes...

Jack Brickey
Community Champion
February 10, 2020

@Patrick Ferraro, you might want to consider submitting feedback to Atlassian via the feedback link in the sidebar.

Tony Rossiter
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 10, 2020

If the ..."parent ="... query runs but doesn't yield results other than the epic itself, this means there are no sub-tasks to the ticket. 

So, in that case I would recommend using: 

key = [epic ticket key] AND "Epic Link" = [epic ticket key]

Hope this helps.  Either way suggested will move the tickets you're looking to move.  

Edit: I fixed the query to use "Epic Link" = 

Suggest an answer

Log in or Sign up to answer