You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am testing greenhopper version 6.1.4.4 on JIRA 5.2.5. What is the primary difference between epic and story. In the docuementation it was not briefly described.
An Epic will incorporate a larger body of work, big enough to need to be broken down into Stories. So the basic difference is in hierarchy, where an Epic is the most general type, containing of multiple, more specific Stories, and eventually (optionally) Sub-tasks of Stories, which describe and track the work on the lowest and most detailed level.
Srinivas,
EPIC vs Story is more towards a methodological question. If you like to understand more about EPIC and Story in Agile methodology, you can review this article here including a brief example:
http://www.mountaingoatsoftware.com/blog/stories-epics-and-themes
Cheers,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think that this question is more oriented toward trying to understand if JIRA/JIRA Agile treats an epic differently than a story. Or if there are features related to epic/story that are exclusive to one or the other.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.