Dashboard gadget projects reported as separate line items

[Chuck Oleary]

I have a dashboard that looks for issues based on 2 different fields for Components and Increments across all of our projects.

The query returns the data just fine and I save the query.

I add  an Issue Statistics gadget to a dashboard and configure it to: Statistic Type of Component.
The dashboard then separates each project into different line item.

How can I get it to report totals for a component and disregard the project?  

[Trudy Claspill · Accepted solution]

Hello @Chuck Oleary 

Components are project-specific. Even if you use the identical visible value for the Component in multiple projects, each Component defined in each project gets a unique ID in the database. The gadget is presenting data based on "unique" Component based on the ID assigned to the Component.

Components are not shared across projects.

I'm not aware of any native Jira way to get data to group based on the visible value rather than the ID for Components in that particular gadget. You might be able to do so with a third party app.

[Chuck Oleary]

Thanks, yet another 3rd party app to do something that should work natively.

The cost of 3rd party apps is getting way our of hand and I'm not going to ask for more money for another bolt on.  The ability to provide meaningful dashboard continues, I'm very frustrated.

I do get that the components have a unique ID in the DB but I'm giving it a query that specifically doesn't even take that into consideration.  Why even ask for the saved filter if the gadget is going do whatever it wants and pull and report on the data?  My query is returned with 37 rows of data but the useless widget decides to add on complexity.

(I also wish there was a way to Accept a questions answer, but accepted as not a viable solution).

[Trudy Claspill]

I don't think the gadget is doing "whatever it wants". The total count of issues (looking at your screen image) is still 37 issues.

It is presenting the data per unique Component, which is how you configured it to present the data.

How is that different than the results of your filter? Are you using an ORDER BY clause in your filter?

[Chuck Oleary]

This is my query:

"PI End[Dropdown]" = 2023.2 AND (issuetype in standardIssueTypes() AND issuetype not in (Epic))

This returns 37 tickets, it doesn't group it and give me different sections based on anything, in this instance Project.
When I add it to any gadget and chose the statistic type of Component it groups and reports on them by project, when I never selected that anywhere.
In my picture above you'll see 3 line items for the component B2C, and 2 each for FIG and C2C.

I also found https://jira.atlassian.com/browse/JRASERVER-8663 with 577 votes but it has been set to "Not Being Considered"
https://jira.atlassian.com/browse/JRACLOUD-8663 is for cloud and has 533 votes, which is still "Gathering Interest"

So can't easily monitor and report during a PI, or PI over PI, how work is progressing and if we are seeing improvements. 
I can drop this in an excel spreadsheet and email a report every day, or, as you say, pay another company for a solution.

[Trudy Claspill]

The gadget is working as designed.

The design of a filter is to present a list of issue which can be optionally ordered. There are no commands that you can add to a filter to "group" results, you can only set the ordering of the list. Your filter does not contain anything that sets the order of the results. 

Even if you set the ORDER BY clause for the filter, that would have no impact on this particular gadget.

The design of the gadget is to group the issues from the filter based on what you select for Statistic Type and give you statistics for each group. You selected Components. That instructs the gadget to group the issues in the filter results by unique Components and provide the statistics per Component. Since Components are unique per project you end up with line items for the B2C Component per project.

In both the filter and the gadget you are still getting the same issues. By design the presentation of the information is different.

There might be a way to create an Automation Rule that could count the number of issue based on the visible value of the Components rather than the unique ID. I haven't tried to work exactly how to do that, so I'm not positive it could be done. If it could be done, then the Automation Rule could also send the results as an email.

[Hannes Obweger - JXL for Jira]

Hi @Chuck Oleary,

first off, I very much understand your frustration about the need for 3rd party apps for what one would expect to be native functionality.  

Just for reference, if you would be open to a solution from the Marketplace, I believe your use case would be easy to do with the app that my team and I are working on, JXL for Jira:

For context, 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) and sum-ups. With these, you can create a report like the above in just a couple of clicks. 

As you can see above, JXL is grouping components by their display name rather than by their ID. You can still do a nested grouping by project, if you'd prefer to do it differently.

Any questions just let me know,

Best,

Hannes