Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].

Migrating Epics

Created by Rosie Jameson [Atlassian], last updated on May 15, 2013 1 minute read

If you were previously using epics on the Classic boards, you can easily migrate your epics to your new boards.

To migrate your old Epics:

Log in as a user with the 'JIRA Administrators' global permission.
Select JIRA Administration from the top bar, then select Add-ons > GreenHopper.
OR, if you are using JIRA 6.0 or later, click the 'cog' icon in the top bar, select Add-ons, then scroll down the page to the GreenHopper section.
Select Classic Migration, then click Start Classic Epic Migration.
Select the project(s) whose epics you wish to migrate, then click Next.
In the Summary popup, verify that the number of epics is what you expect, then click Migrate.

Screenshot - successful Epic Migration

Please note that this migration allows you to move your existing epic links so that you can start managing epics and their issues on the new boards. Epic links created on Classic boards after the migration can be migrated at a later stage..

Technical note: the migration process will find issues with an issue key in the 'Epic / Theme' field and copy it to an 'Epic Link' field (unless the issue already has an Epic Link field). For more details about these fields, please see GreenHopper JIRA Configuration

関連ページ

greenhopper-admin

10 Comments

Jeff Patterson
Feb 11, 2013
When you say, " will find issues with an issue key in the 'Epic / Theme' field and convert it to an 'Epic Link' field", does that mean it will create the Epic Link field entry in addition to the original Epic/Theme field, or will create the Epic Link entry and delete the older Epic/Theme link? Thanks.
1. Michael Ruflin
  Feb 15, 2013
  In addition. The migration process only reads the Epic/Theme field data, it does not alter or delete it.
Hans-Hermann Hunfeld
Feb 11, 2013
Is this only available in download version or where can the epic migration handled in ondemand?
1. Rosie Jameson [Atlassian]
  Feb 12, 2013
  This will be available when OnDemand is updated to GreenHopper 6.1.3 (currently scheduled for next week)
Anonymous
Feb 13, 2013
As far as I know with the new boards it is not possible to assign Epics to an Epic (using Sub-Epics) and also it is not possible to assign an Issue to multiple Epics. Since both is possible with Epic/Theme fields and we practice these cases, I would like to know how they are handled. Will an Issue that has to Epic/Theme entries also have to Epic-Link entries? Will Epics still be linked to a parent Epic it had with Epic/Theme and, will this be displayed in the new Boards somehow?
1. Michael Ruflin
  Feb 15, 2013
  You are correct, only one hierarchy level is supported at the moment, plus issues can only be assigned to one epic at a time. In your specific use case I would probably use normal issue links to achieve relations between epics.
  In regard to the migration: epic to epic links will not be migrated. In the case where a story links to two epics we just migrate the first epic in the Epic/Theme field (in alphabetic order I believe).
Andrei Samuta
Feb 26, 2013
Please describe how to migrate links for all projects. If you have more than 100 project select them all from list looks very boring.... And actually not possible. (I can select only about 35)
1. Rosie Jameson [Atlassian]
  Mar 04, 2013
  Can you please contact http://support.atlassian.com for assistance? Many thanks
GertjanA
Mar 01, 2013
It looks like this is only migrating open stories, after migrating all the closed stories that have a filled Epic/Theme field do not get a corresponding epic-link
This is severly impacting our reporting on those epics
Please Advice how to solve this
1. Rosie Jameson [Atlassian]
  Mar 03, 2013
  Can you please contact http://support.atlassian.com for assistance with this? Many thanks