Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Recommended way of associating an issue with a specific functionality

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?

1 comment

Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 07, 2020 • edited

Hi @Carl-Erik Kopseng ,

As you said, there are different ways to group issues. I would recommend the usage of components

With components, the advantages can be

  • Project admin can manage components
  • These components can be used to categorize issues and use them in filters
  • Each component can have a project lead.
  • Easier to implement. Add the component/s field to the create issue screen and make it mandatory.  


Log in or Sign up to comment