I am attempting to bulk move 20+ EPICS from one project to another. In doing so it is not prompting to include child issue types. If I jql search for EPIC LINK in (JS-1, JS-2, JS-3) etc. id does not include sub-tasks. How do I bulk move epics and include all issue types and subtasks from one project to another?
We are on prem not cloud.
Hi @Jason Steele ,
If you move parent ticket (standard issue types) to other projects. Sub-tasks also gets moved to the other project.
While moving system will ask for the destination issue type of sub-task. You no need to filter them. If you move parent ticket, automatically sub-tasks also get moved.
Thank you. for some reason I am not getting that prompt of subtasks. When I move EPIC it is only prompting me for the EPIC and not any tasks underneath. I tried a test and it moved the epic only then I had to find the associates issues under and move those separately. I know this is non-standard so we are investigating on our instance. Have you seen this before?
Let's say the search is assignee = jsteele AND issuetype = EPIC
It returns 20 epics (correct). If I click on an epic (JS-1) it shows all the issue types associated with it. If I try to bulk move epics it isn't giving me the prompt for all issue types. It is only showing EPIC. If I move those it just moves the epic and the issues all stay in the original project.
Got it. You need to move everything returned by the filter and not just the Epic. Unless the "Issue In Epic" is a direct sub-task of the Epic itself, just moving the Epic will not move the issue(s) within the Epic.
So basically you need to create a filter that returns all the issues in the identified Epics and the Epics... and not just the Epics.
try this filter
"issue in childIssuesOf(Epic Name)"
or this one
parentEpic in (EPIC-1, EPIC-2)
this is arguably a workaround, but I think your problem would be quite easy to solve with the app that my team is working on, JXL for Jira.
JXL is a full-fledged spreadsheet/table view for your issues that, among many other things, supports issue hierarchies. So what you could do is,
This is how this would look in action:
(In the future, we may add a "move" feature directly to JXL - ideally through inline-editing, just like you can inline-edit other fields - but for now it's at least easy to invoke the native Jira flow.)
Hope this helps,
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