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.
True, that's a fourth category to ask about!
I believe @Trudy Claspill is correct. It is a field appearing in the List View of the Work Management board.
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.
It looks like you're new here. Sign in or register to get started.
