I am using jira cloud. I am moving an entire project. Why is the EPIC name required on the move when I specific to retain the original? Is this going to overwrite my epic values to the SAME value for everything I am moving? I can move them one at a time but this seems dumb.
Thank you for reaching out.
The Epic name is required by default to all Epics in your instance. In fact, an Epic can not be created without an epic name, however, once the epic is created and set with any value in the Epic name, the field does not need to be edited anymore.
That being said, I believe that maybe you are facing this error when bulk moving your issues because of the following reasons:
1 - The project that you are moving the issues from is a Next-gen project and the target project is classic. Next-gen does not have the Epic name field, so it is required that you set the Epic name when mapping them to Epics from standard projects.
2 - During the bulk process, you are mapping an issue from standard type (Task, Story, etc) to be an Epic in the new project.
If the information above does not clarify your current scenario, please provide us with the JQL query you are using to move your issues and a screenshot displaying how you are setting the fields during the bulk process. P.S: Make sure you've hidden all the sensitive information from your screenshots before posting it.
Remember that time you realized it was possible to refresh your Jira data in Google sheets with just one click? What if we told you that you can now get the latest data with no clicks at all?! Zero! ...
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