Which is better to group tickets? Epics or Labels

Nelson Loia Jr_
Contributor
March 25, 2024

Hi!

    I already connected JIRA & Airtable through API Token, for reporting and management.
     But in AirTable I need to group the tasks using what we call "Modules" and "Sub-Modules".
     At first I tought to connect same ticket to more than one Epic, but I found that it's not possible,
here: https://community.atlassian.com/t5/Jira-Software-questions/Assign-Multiple-Epics-in-a-single-issue/qaq-p/2191915#:~:text=You%20cannot%20do%20that.,%22parents%22%20of%20the%20issue.   

     Now I'm thinking to use the JIRA "Labels" to organize the tasks based in our modules classification.
     The idea is to create labels based in the "Modules" and "Sub-modules" we have, because in JIRA we have more than one column called "Labels" (print). 

Print: "Modules" & "Sub-Modules" in JIRA tickets for an specific project: 
JIRA Labels.png

Please, is it a good approach?|
Is there other ways to organize the tickets in JIRA that it also reflect in AirTable registers?

I thank you all in advance.

2 answers

1 vote
Nikola Perisic
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 25, 2024

Welcome to the community @Nelson Loia Jr_ 

As I can see from here, we are talking about the grouping. Here we can use two things:

  • Labels - which can be used worldwide
  • Components - work better with grouping within the projects

Reference from: https://community.atlassian.com/t5/Jira-Software-questions/Difference-between-Components-Vs-Labels-with-example/qaq-p/2270663

Nelson Loia Jr_
Contributor
March 25, 2024

Hi!
Thank you for the prompt response @Nikola Perisic 

 It seems that in my case the Components fits better. I'll double check.

Best regards.

     

Like Nikola Perisic likes this
Nikola Perisic
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 25, 2024

I would personally go with components especially when it comes to grouping.

Like Nelson Loia Jr_ likes this
0 votes
Hannes Obweger - JXL for Jira
Atlassian Partner
March 26, 2024

Hi @Nelson Loia Jr_

welcome to the community!

I trust that components are a good fit for what you're looking for! Just because you're looking for ways of grouping your issues and have a background in Airtable, I thought you might be interested in the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features - some of which you may be familiar with from Airtable - including support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

This is how it looks in action:

group-by-components.gif

This is really just one of a virtually endless number of possible views and reports - you really have full flexibility on how you organise your issues.

Any questions just let me know,

Best,

Hannes

Nelson Loia Jr_
Contributor
March 26, 2024


Thank you @Hannes Obweger - JXL for Jira  for the input.
I'll take a look since I finish this task

Best regards.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events