Epics vs. Stories

[Sutton, Andrew]

When you all are creating new tasks do you create them as Epics or Stories?  I'm still a bit unclear about the verbiage...

Thanks for putting up with this Jira Rookie.

Andrew

[Michael Andolfatto · Accepted solution]

Hi @Sutton, Andrew ,

Epics are introduced to Jira as a part of Jira Software which follows Agile principles. There's a default hierarchy present within Jira Software which looks like:

• Epic
• Story (Any standard issue type - e.g. Story, Task, Bug, custom issue type, etc.)
• Sub-task

Each parent issue type is comprised of one or more children which each breakdown the parent's work into actionable items. It will depend on how you are using your Jira project, so I'd recommend getting in touch with your project or team lead to verify, but generally one of two are true:

1. Your team follows an Agile methodology such as Scrum, and Epics are created to represent work items that may take several weeks to complete and will not fit within a work iteration (Sprint)

2. Your team does not follow Agile but still uses the base hierarchy in which case Epics may still represent an aggregate of work/tasks but require input specific to your organization/team.

[Fabio Racobaldo _Herzum_]

Hi @Sutton, Andrew ,

usually an Epic is an high level feature that should be implemented through multiple stories associated. This is a common approach for the Agile methodology.

Please take a look to this article that could help you on that https://www.atlassian.com/agile/project-management/epics-stories-themes

Hope this helps,

Fabio

[Sutton, Andrew]

Another excellent resource.  Thank you Fabio.

Andrew