Archiving Epics

[stephen.causon]

Is there any way to Archive an epic? I created a new project, called "Archive" with the intention of just moving Epics across to the Archive project. Unfortunately, when I do this, it strips out all the data in the custom fields I created in the epic type - even if the new "Archive" project has fields of the same name. I would have thought it would have transferred the data across, but it doesn't.

Is there a better way of archiving epics and removing them from the "Roadmap" display?

[Petter Gonçalves]

Hello Stephen,

Per your description, I believe you are talking about a next-gen project in JIRA. Is it correct?

The next-gen template is a new lab feature of JIRA where our developers are still working to implement some useful features, including the retainment of Custom fields when migrating from one project to another.

Also, the roadmap feature is based on the same board filter, which is not customizable in next-gen. We have a feature request to implement the functionality you need:

Hide Done Epics in Roadmap

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

For now, the best option I can recommend would be to keep transitioning the issues to the archive project as you are doing, however, copy the value of the related custom fields to the description of the Epics.

Performing the steps above, the related information of the custom fields in the archived Epic will be available in the Description, although I understand it will not be an agile but a temporary solution.

Additionally, Automation Lite for JIRA Cloud app might help you to automatically add the custom field values to the description field, by referencing the values of the fields with Smart Values in the description.

Let me know if you still have any questions.