Documentation for GreenHopper 5.5.x . Documentation for other versions of JIRA Agile is available too.
GreenHopper is now called JIRA Agile. Learn more.
An epic is essentially a large user story that can be broken up into several smaller user stories. Epics are typically used to capture large and complex items from the product backlog that are low priority and are yet to be defined in great detail.
Epics are implemented in GreenHopper via a JIRA custom field of type 'label', which are used to associate cards with a parent epic.
As of GreenHopper 5.3, your GreenHopper project must use the 'Scrum' template to successfully work with Epics. Upon applying this template to your GreenHopper project, you will then be able to properly associate Epics with other GreenHopper issue types and vice versa.
Overview
Content Tools
Apps
Log a request with our support team.
Raise an issue for our developers.
See answers from the community.
Tweet, blog and update our documentation.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.