How did I end up with two EPIC Issue types in my project and how do I get rid of the wrong one?

[Rick Wahlberg]

It's causing my Epic loads to fail, only populating Issue Summary but not Epic Name?

[Jack Brickey · Accepted solution]

it seems that you or someone created a custom field named Epic. go to project > project settings > issue types > actions > edit issue types and in the left column "issue types for current scheme" you should see two Epic issue types. You need to find the one that is custom and drag it to the right column and save it. However, before you do that I would run a JQL that included the incorrect issue type and bulk move them to the correct default Epic type. Once done you should then delete this extra issue type.

[Rick Wahlberg]

This is cloud.

What I did do is build a new Issue Type Scheme, associated it to the project.

In the association it asked me to convert the 'bad' epic type issues. I did so to Task and then updated them.  

I'm not testing a new EPIC load using format

Epic Name, Summary, Issue Type.

Hopefully it will work this time.

Thanks for your help though. 

In cloud not sure how I'd build a JQL for the wrong issue type as they appear to have the same name.  I'd have to key off name and description I guess.

It is a problem for another project.  I may try either solution.  Trying to not be disruptive.  I'm hoping that any epic links would not be broken when I do.

[Rick Wahlberg]

I'm not sure but it seems that my default Epic Name field is not associated with any issue types?

[Rick Wahlberg]

PS.   The failure is that Summary is populated and not Epic Name.

If edit/change the Epic to a Story, then back to an Epic

Then Edit the Epic. it presents an opportunity to enter Epic Name

That said, it means no bulk load for epics.  Just type them in, or live with bulk load and correct as above.