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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Current »

An epic captures a large body of work. It is essentially a large user story that can be broken down into a number of smaller stories. It may take several sprints to complete an epic. 

Epics provide you with an additional hierarchy of story management, providing planning guidance for groups of issues within, or across, projects. This allows ScrumMasters and Product Managers to measure important groups of issues that are all related by a common theme.

See Creating an Epic and Adding an Issue to an Epic.

(Note: In JIRA, epic is a searchable field — see the JIRA JQL documentation for details.)

For more on Epics you may want to read over these two excellent articles:

  • No labels



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.