The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
There are lots of ways to groups and organize issues in Jira, but we are a bit lost as to how to make use of these features for a certain use case.
Currently, I think we are misusing Epics to group issues relating to a functionality in the app. For instance, tasks relating to auditing is put in the "Auditing" epic, "Risk Screening Form" has tasks related to risk screening form, etc.
While some of these are OK to have in a an epic, such as the risk form example, the problem is that new ones are added and the epic can kind of never be closed. So I was thinking of double-categorizing them by using Epic (for the original bigger task) and something else that will stick around no matter the actual status of the task. So either "Component" or "Label", not sure which is better suited.
I have tried searching the docs for the intended purpose of either category, but I have been unable to find the intent of either.
Could you enlighten me?
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events