Group tasks based on Component

Karrie Dash_ovl3wg

We use components to organize our tasks (Frontend, Backend, Security, Server, Database, etc..).

When giving updates or reviewing tasks, I would like to see the tickets grouped together based on their component, but all on one page. But, I don't want to go into the Components page and open each component individually.

A view similar to a board with the components as the swimlane but without having to write a query for each component. But this does not work because tickets may have multiple components and it only shows under 1 component, not all.

 

I could create a Confluence page and use the Jira Issues macro, but that means anytime I add a new component, I have to add a new query in a macro.

 

There is a "Single Level Group By Report" that can use the Component field but the report UI cannot be customized.

 

Is there a better option or view available?

Hannes Obweger - JXL for Jira

Hi @Karrie Dash,

I'm not personally aware of a built-in view in Jira that would do exactly that. The best that I can think of is to order your issues by component in JQL (using an ORDER BY component clause), but that's also far from ideal.

Alternatively, if you're open to solutions from the Atlassian Marketplace, you'll have more options available. E.g., you use case should be very easy to solve using 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, including support for issue grouping by any issue field(s). This is how it looks in action:

This also works across projects, grouping together components with the same name from different projects. Once you've set up your sheet, you can embed it into Confluence in just a couple of clicks.

I should also add that issue grouping plays well with JXL's other advanced features, such as support for (configurable) issue hierarchies, sum-ups, or conditional formatting. 

Any questions just let me know,

Best,

Hannes