JQL filter Advanced search on a specific component

[Shantall Légaré]

Hi! I tried to search for one specific component in my project but most of my tickets contains more than one component and it results of a graphic with all components instead of just the one I need...

ex:Several tickets contains more than one components:  "DP", "EQ-1", "EQ-2"
I'm looking to have only tickets who has "DP" but, because "EQ-1" and  "EQ-2" are also in the tickets, the graphic show me all the components and worst, they are double count!

I use this:
project = XYZ AND component in (DP-C, DP-T, DP-E) ORDER BY Rank ASC

Somebody can help ?
Thanks!
Shantall

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

There are two parts to what you are seeing.  There is a search, and a report.  Most reports work off searches of some sort, and when I say "report", I'm including gadgets on dashboards, boards, the issue nvigator and the rest - anything that displays issue information.

It is important to understand that searches find issues.  They have nothing to say about what a report does with them.  They really are just "find me issues that match these criteria" and it simply returns a list of issues.

So, when a report runs a search, it then reads through the issues for what it is looking for and shows it to you.

From your question, I suspect you are looking at one of the gadgets that does statistics on the issues. 

This is easier to explain with an example, so, let's say you have:

• A search for "project = ABC"
• Issue ABC-1 has components of DP
• Issue ABC-2 has components of EQ-1
• Issue ABC-3 has components of EQ-2
• Issue ABC-4 has components of EQ-1 and EQ-2
• Issue ABC-5 has components of DP, EQ-1 and EQ-2

So, when you use a statistic type gadget that summarises on components, it is working with

• DP: 2
• EQ-1: 3
• EQ-2: 3

Because that's what the data is.  It's not "double counting", it's counting accurately.

There's no way to flatten this out - the report would be inaccurate if it did not show you the data this way.

[Shantall Légaré]

You're right, I'm using a widget to show how many tickets for each "DP" we have to manage.

Your example is almost right.  Only DP-1, DP-2, DP-3 are missing.

Do you have any other suggestion to obtain a graphic view only on my DP's components?

Thanks for your help!

[Nic Brough -Adaptavist-]

I kept the example simple, only working with three components.

There is no way to do a report that is inaccurate like this.  A report will always give you a count of the components when they exist.

[Nic Brough -Adaptavist-]

The only way I can think of "fixing" this would be to stop using multi-select lists.  Allow only one "component" per issue.  If you have a short list of a couple of distinct components, you could do something like

• DP component: Single-select list, options 1, 2, 3
• EQ component: Single-select list, options 1, 2, 3
• Other component: Single-select list, options 1, 2, 3

[Shantall Légaré]

Thanks for your time and experience!
I will discuss this with the team because we have so many components already in the JIRA that it would be a massive work to change all this.

Thanks for your help!

[Trudy Claspill]

What graphic are you creating? Are you using a native Jira feature or something else?

Do you want to exclude the issues that have those other components, or do you just not want to show those components or double count the issues?

If you want to entirely exclude issues that have both DP* and EQ components, then you need to add a clause to your filter to exclude issues that have the Components that you don't want to include.

and component not in (EQ-1, EQ-2)

[Shantall Légaré]

My goal is to show with a widget how many tickets we have, by DP,s:

Let's say we have:

• A search for "project = ABC"
• Issue ABC-1 has components of DP-1
• Issue ABC-2 has components of EQ-1
• Issue ABC-3 has components of EQ-2 and DP-2
• Issue ABC-4 has components of EQ-1 and DP-1
• Issue ABC-5 has components of EQ-1 and DP-2
• Issue ABC-6 has components of DP-2, EQ-1 and EQ-2

I would like to see in my graphic that we have 2 tickets in DP-1 and 3 tickets in DP-2, without showing components EQ-1 and EQ-2....

Thanks for your help!