Epics are implemented in GreenHopper via labels, so you will first need to install the JIRA Labels plugin as it is not included by default. Labels are used to associate cards to a parent epic. You will need to set up a custom label field in JIRA and then add this to your card templates. Once you have added the label to your card template, you can specify the issue key for the parent epic in that label field on each related card.You can then view all cards related to that epic via the GreenHopper search.
We recommend that you set up a new issue type to use for epics. This is not essential, but it will help you to distinguish epics from other issue types like stories.
For example, you may create an issue for an epic (with the 'Epic' issue type, if you've set up that issue type) and a number of issues for the stories, tasks, etc, to be associated with the epic. The stories, tasks, etc, would then be associated with the parent epic by specifying the issue key of epic in the label field on the cards for the stories, tasks, etc.
Setting up epics for your project is a simple four-step process:
- Install the JIRA Labels plugin
- Create an 'Epic' issue type in JIRA
- Create an 'Epic' custom field in JIRA
- Configure your cards to use the 'Epic' custom field
Creating an 'Epic' Issue Type in JIRA
As mentioned above, creating an 'Epic' issue type is optional. If you don't want to do this, you can simply configure your cards to use the 'epic' custom field as described below.
To create an 'Epic' issue type,
Creating an 'Epic' Custom Field in JIRA
As mentioned above, creating an 'Epic' custom field requires the JIRA Labels Plugin to be installed.
To create an 'Epic' custom field,
Configuring your Cards to Use the 'Epic' Custom Field
To configure your cards to use the 'Epic' custom field,