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.
Please clarify the difference between Epic Vs Category
We need a bit more detail.
Epic is usually the layer above issue - an Epic contains a collection of issues.
Category is a lot more vague - project category, issue category or epic category?
Category might be a reference to the Category field that is a built-in field for Work Management issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
True, that's a fourth category to ask about!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I believe @Trudy Claspill is correct. It is a field appearing in the List View of the Work Management board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, great, we can clarify that.
Epics and Categories have a similar reason to exist - they are for grouping issues together for some reason.
Where they differ is that Epics are primarily an Agile artefact, used for grouping together a large pile of stories from across your entire issue tracking system(s), all the stories that need to be considered together to achieve a single goal (yes, they should span systems when you've not yet managed to get everyone on to the same one properly)
Categories are much the same - you're grouping things together because they have a strong relationship. But, not because they are part of the same goal, more because they have a lot in common.
To use a recent example and hugely over-simplify:
The Epic can now be closed, people have attended, survived, suffered Team-'flu, done the work on contacting leads and and and. But it's still in the same category as the last 20 Team events.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Excellent example, @Nic Brough -Adaptavist- ! Thank you very much. With Epics, I can go to any Epic view and see all the related issues. With Category, there is no way to do the same in Jira Work Management, correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Correct, the category is more like a field than an Epic grouping. So while there's no "show me this category", you can of course search for it - JQL (and the basic search, and a lot of the reports) let you say "list the issues in this category".
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.