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
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
I just want to understand the structure of Jira. Is Epic specific to the Jira instance or specific to the jira project? could there be two distinct epics in two different projects? or they are shared and the same in the different projects?
Hi @Osama Al-Areky ,
Epics are specific to a Jira project and you can have multiple distinct ones in both the same project or across different projects.
Take a look here to learn more about Jira Software Epics: https://www.atlassian.com/agile/tutorials/epics
And here to learn more about how to use Epics in an Agile context: https://www.atlassian.com/agile/project-management/epics
I hope this helps.
The 'beauty' of Jira is in its flexibility. This is both a benefit and a curse at times. You can, in theory, make any of those work.
However the more common situation, from my experience, is that you have multiple epics in a project.
Below is some documentation I put together for a client a while back and I am providing it as an example, but it should not be taken as standard industry wide definitions. Please let me know if it makes it clear for you. If not, Ill try to explain.
Note: traditional agile methodology states that you shouldnt define things with amounts of time but that team needed a stricter definition hence stating things like "month" and "two weeks".
Issue Type Definitions
Within Jira, there are a variety of issue types. Standards are required to be followed in order to maintain consistency and company-wide understanding.
Project - Cleaning the house
Epic - Cleaning the kitchen
This is a sufficiently complex activity that has a lot of work within it so it is our epic. If you had that alone then that is not enough information to proceed.
Each story is a complex task in itself and requires sufficient time to do. It can only be broken down into very small sub-tasks. Each piece has a clear singular deliverable and you will know when it is delivered.
The sub-tasks are small items but they go into completing the story whereas checklist items are tiny things that need to be confirmed or can be done very quickly. The checklist for the fridge is just areas of the fridge to ensure that nothing is missed, while the subtasks are activities that need to be done but can go to other people. You may clean the fridge but your partner throws out the old food.
Tasks are smaller than stories and cannot be broken down as easily. They are straightforward and lack the complexity of a story but still result in a single deliverable.