How can I group lookupIssues results by component, and report size of each group?

[Elbert Grigoriy]

How can I group lookupIssues results by component, and report size of each group?

[Trudy Claspill · Accepted solution]

Hello @Elbert Grigoriy 

Welcome to the Atlassian community.

Component is a multiple-selection field so you cannot effective group issues based on Component.

How would you expect the results to appear for a issue that has multiple component values?

Can you tell us about the problem you are trying to solve, where you think this is the solution? Perhaps we can suggest an alternate solution.

Also lookupIssues is an element of Automation Rules. What is the purpose of your automation rule? Can you share screen images to show us the entire rule?

[Elbert Grigoriy]

Team plans to use "Component" field to store only one value. Aim is to be able to find out how many items (jiras) were handled per each component.

[Trudy Claspill]

Thank you for that additional information.

Why are you using an automation rule to gather the information? 

[Elbert Grigoriy]

Yes, aim of automation is to collect statistic on areas (components) where most jiras were originated to identify where team should look for potential improvements.

[Trudy Claspill]

Thank you. Can you explain though why you are trying to do this with an automation rule as opposed to another method.? Why not use a saved filter and present the information within Jira in a Dashboard, for example.

[Elbert Grigoriy]

Filter would require knowing names of components in advance. Goal was to run automation job to collect required statistic and email results. 

Still, if it is possible to present information about number of jiras handled per component in previous month using dashboard or any other way, please share steps how to do it.

[Trudy Claspill]

Why does the filter need to know the names of the Components in advance?

Create a filter that selects the issues you want; i.e.

project=CS and component is not empty

Add in the criteria that means "were handled". Does that mean that were resolved? Does a time frame need to be applied?

Save your filter. 

In a dashboard add a Two Dimensional gadget.

Select your save filter as the source.

Set one Axis to Component. Set the other to something that makes sense to you. I chose Issue type.

The output will look something like this:

[Elbert Grigoriy]

Thank you, I will try proposed approach.

[Trudy Claspill]

Let us know how that turns out!

[Elbert Grigoriy]

I used "Work Item Statistics" gadget. That gave me total numbers needed without breakdown.

[David Nickell]

@Trudy Claspill  seems to have covered everything you need. 

1. Keep in mind components are defined per project.  Even if you use the same component name in two projects they are unique.  For example "ProjectA.Mobile" and "ProjectB.Mobile" are unique.
2. It sounds like components are important enough in your organization that you may want to have a confluence page that provides your technical specs and functional requirements.   On that page you could also have a Filter Results gadget that would let you see all of the tickets touching your component over time. 
3. The reporting that you are trying to do will help with cost estimation in the future.  

If you get interested in a deeper dive on your components, you can look to the REST APIs to help collect the details you want.    This is also helpful if you need to integrate with another application that is component affecting  (Like monitoring or deployments). 

Good luck 

[Danut M _StonikByte_]

Hi @Elbert Grigoriy,

Have you tried the Jira gadgets such as Work Item Statistics or Two Dimensional Filter Statistics? They both support the Components field and if you configure them with a filter that returns the issues from past month you will get what you want.  

Looking at the need you expressed "to present information about number of jiras handled per component in previous month using dashboard or any other way, please share steps how to do it.", you can have something like this:

To obtain this, you should configure the Work Item Statistics gadget in this way:

If you want something more advanced, such as displaying a chart, you will need an app (plugin) from Atlassian Marketplace.

If you want to try an app, I would recommend taking a look over the Pivot Table & Pivot Chart gadget offered by our Great Gadgets app. With this gadget you can dsplay the info in many ways: as a table, as a heatmap, or as a chart. And it can display data for past moths. 

For getting a chart like this, the gadget should be configured like this:

Hope this helps. fee free to contact us at support@stonikbyte.com if you need any help with the setup of our gadgets.

Danut