Two-Dimensional Filter Statistics Gadget

Hi Atlassian Team,

 

JIRA supports Multiple values of field Test Case Status , currently users use same field to track status of different releases. Lets say we have two parallel release Rel_X and Rel_Y and test case TC_01 is applicable for both the releases so got executed in both and to track its execution in both the releases generally user marks them as Pass_Rel X, Pass_Rel Y respectively. So final value of Test Case Status for TC_01 is Pass_Rel X, Pass_Rel Y.

Now if we want to track status of Rel X (how many test cases passed, how many failed ) ,we will apply filter like   (project = TCM AND "Application Name" = MOSO AND status != Closed AND Module = Sync_Kracken and "Release Version" = "Rel X" and "Test Case Status" = "Pass_Rel_X" ) this will return us list of test cases passed in Rel X.

Let's say TC_01 is passed in both the releases so have Test Case Status value as (Pass_Rel_X, Pass_Rel_Y). So TC_01 will come in results as it satisifies the filter condition.

If we use same filter mentioned above in Two-Dimensional Filter Statistics Gadget and  select an X axis field to be Test Case Status then it displays all values of Test Case Status  for TC_01 in the Gadget (both values Pass_Rel X, Pass_Rel Y ) While we need status only of Rel_X and that is what we mentioned in our filter also. So it would be great if we can get a sub option to select any one value out of multiple values of Test Case Status field, so that we can track execution status of test cases per release. 

Thanks

1 answer

This widget could not be displayed.

>JIRA supports Multiple values of field Test Case Status

You'll need to explain how it is doing that - is it a multi-select field or something else?  Something coming from an add-on?

Hi Nic,

 

Test Case status field template is used as label_searcher.

I am not able to attach snapshot.

Field description:

Test Case Status:  
      •  
      •  

Begin typing to find and create labels or press down to select a suggested label.

 

 

Ok, that makes sense.  The problem now is that you're expecting the gadget to be configured with information you are not giving it.

You will need to refine your filter to report on what you actually want.  Doing a secondary selection on the gadget level is quite a lot of complex coding you'd need to add, and it's inefficient and unclear.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

229 views 3 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you