Use result of Jira chart in another chart's query

[adrian8535]

Hi

I have a two dimensional chart with filtered issues. X axis is status. Y axis is Components. 

I have another similar table (same X Y axis) and I want to show in it ONLY Components that do not exist in first table. 

Can I do it without using any external plugins and how?

If some plugin is required, pls provide which one and how to do it with it.

Thanks in advance!

[John Funk]

Hi @adrian8535  - Welcome to the Atlassian Community!

No, that is not possible. Out of the box Jira does not have the ability for one gadget to use information from another gadget.

[Daniël]

Hi @adrian8535 

are you making use of the Jira dashboard gadget 'Two dimensional Filter Statistics'?

Can you define what is meant by "only components that do not exist in the first table"? What is the reason they don't exist in the first table?

Depending on your answer is might be possible using filters in which you make use of "filter not in".

[adrian8535]

Hi @Daniël 

I click it like Insert -> Jira Issue/Filter -> Jira Charts -> Two Dimensional.

In 1st table I want to have list of released components (issues which have component set and OPTIONALLY label "config" set).

In 2nd table I want to have list of redeployed components (issues which have component set and label "config" set but they DO NOT exist already in list of released components (1st table)). This is because released component is redeployed anyway. So in 2nd table I want to find components which had only config changes done for the upcoming release and need to only be redeployed, without releasing new version.

I tried to create a filter (fixVersion = "release/2024/06") and use it in 2nd table (fixVersion = "release/2024/06" and labels = "config" and filter not in filter) but it filters out all issues with fixVersion set to release/2024/06 and final output is 0 issues.

[Daniël]

@adrian8535 

ok, so you are using the Jira/Issue macro in Confluence.

Please share the exact both JQL's.

[adrian8535]

Did small corrections and now in 2nd table I have all components with config label set, also ones that already exist in 1st table.

1st table:

project = MYPROJECT AND fixVersion = "REL_2024_3" AND issueType in (Bug, Story) and labels != "config" ORDER BY Component ASC

I created and saved filter as MY_FILTER:

project = MYPROJECT AND fixVersion = "REL_2024_3" AND issueType in (Bug, Story) and labels != "config"

2nd table:

project = MYPROJECT AND fixVersion = "REL_2024_3" AND issueType in (Bug, Story) and labels = "config" AND filter not in (MY_FILTER) ORDER BY Component ASC

[Daniël]

see below. How does my issue data differ from yours?

Since label "config" is optional in the first JQL it might mean the field 'label' is empty so I would advice you to consider extending the filter "Released Components":

 fixVersion = "REL_2024_3" AND component IS NOT EMPTY AND (labels = "config" OR labels IS EMPTY)

I used the following data set:

Issue Type Issue Key Summary Status Label Fix Version Component

Bug MC-26 issue 26 summary Backlog notconfig REL_2024_3 Component 2

Bug MC-25 issue 25 summary Backlog config; notconfig REL_2024_3 Component 2

Bug MC-24 issue 24 summary Backlog config REL_2024_3 Component 2

Story MC-23 issue 23 summary Backlog None REL_2024_3 Component 2

Bug MC-22 issue 22 summary Backlog notconfig REL_2024_3 Component 1

Bug MC-21 issue 21 summary Backlog config; notconfig REL_2024_3 Component 1

Bug MC-20 issue 20 summary Backlog config REL_2024_3 Component 1

Story MC-19 issue 19 summary In Progress None REL_2024_3 Component 1

I used the following JQL's:

1. Filter name Released Components 
   • Filter JQL project = "My Project" AND fixVersion = "REL_2024_3" AND component IS NOT EMPTY AND (labels != "config" OR labels IS EMPTY)
2. Filter name Redeployed Components
   • Filter JQL project = "Mailbox CI" AND fixVersion = "REL_2024_3" AND labels = "config" AND component is not EMPTY AND filter != "Released Components"

My result in Confluence using the Two dimensional chart:

[adrian8535]

And this is exactly what I do NOT want ;) In your case, table od redeployed Components should be empty, because Components 1 and 2 are already on released Components list, so they do NOT need to be redeployed.

[Daniël]

Yes that was my conclusion as well. Can you tell me, as asked above, How does my issue data differ from yours? ;)

[adrian8535]

My issue data looks like below:

Issue Type Issue Key Status Label Fix Version Component

Story ST-35 issue 35 Done None REL_2024_3 Component 1
Story ST-36 issue 36 Done config REL_2024_3 Component 1

Story ST-37 issue 37 Done None REL_2024_3 Component 2
Story ST-38 issue 38 Done config REL_2024_3 Component 2

Story ST-39 issue 39 Done config REL_2024_3 Component 3

Tables should look like below:

Released components:
Component 1
Component 2

Redeployed components:
Component 3