How do I bulk change other type of issues into epics?

[Peter Callies]

We have hundreds of New Feature issues (a custom issue type) that I want to change to be Epics. Naturally, I want to do this in bulk, not one at a time. How can I do this given the required Epic fields are not part of any other issu type (Epic Name, Epic Colour, Epic Status)?

[Nina - Phan Thanh Noi]

I have the same issue, how can I link 100 task to an Epic with bulk change? 

JIRA prepare "Change Epic Name" field but it doesn't work, have to use "Change Epic Link".

But "Epic link" is not shown anywhere. Jira need to write an instruction how to get Epic Link to solve the problem. 

Thanks.

[MJ]

If you can group the issues that you want to set to a specific Epic with a single search query, you can use the bulk edit option in the issue navigator to change the Epic Link or Epic/Theme of all of them at the same time. Please look here for more details on bulk changes.

If you want to change the issue type of a bulk of issues, you can use the bulk move option to move the issues within the same project, but to another issue-type, in your case Epic. Please look here for more details on this.

[Peter Callies]

Mick, thanks for taking time to respond. Re-reading my original post, I see that I didn't do a good job explaining what I'm trying to do. I used the JIRA term "move" to describe my needs instead of writing that I really want to change New Features into Epics.

I don't simply want to associate stories (or any other type of issue) with an Epic. I'm trying to get rid of the New Feature issue type since JIRA Agile doesn't support a three-tier model of Epic->Feature->Story.

I'll edit my original post to make my intent more clear.

[Lucid Software]

I have the same need. I should add that Jira does support a three tier Epic -> Story -> Sub-task

[Dominic Giroux]

Ok, ran into this today.  Best solution I came up with:

• Did bulk move on the custom issue type to change it to Epic
  • Set the Epic Name in bulk to" Temporary - Will update from Summary"

This allowed me to complete the move successfully, but with all new Epics having the same name.

Then I ran a scriptrunner console script that looped over these converted issues and set the Epic Name using the Summary value, effectively doing what a smart bulk update should allow to begin with (ability to use an existing field value to set another).

[Crystelle S]

I was looking for information for the bulk move to issue type Epic (all Epics inheriting the same name) and found this - https://jira.atlassian.com/browse/JRASERVER-41733

For cloud folks - https://jira.atlassian.com/browse/JRACLOUD-41733

[Maik Lieweries]

I'm in the same situation and have to change ~300 issues of another type to type epic. "Epic Name" is making it to a not automatic step. I opened a support ticket to get an answer and pointed to this question, too.

[johnlundberg]

Did you get an answer to your support ticket Maik?

I am having the same issue

[Evans Munene]

This issue is two years down the line. Having the same issue.

Is there a solution yet?

[Heinrich Graupner]

I have the same problem now with no solution from jira?