In JIRA Two Filter Dimensional gadget, the fix version is showing multiple times.

[Prasad Andrews]

Hi Team,

We are using Jira Two Filter Dimensional Gadget, the fix version is shown multiple times if it’s used in different projects.

For example, I have 5 projects am I using the same fix versions for all the projects. But when added the gadget in dashboard the fix version is showing multiple times.

Please find the attached screenshot.

[Sathish Muthukrishnan]

Hi @Andy Heinzer ,

I exactly have the same problem, we have product release that span across projects. To make it simple, a product version 1.0 will have multiple project. Tried to pull a report based on release version and seeing duplicates. I know there is already a ticket raised and deferred to fix due to low traction. Things are changing rapidly and do you guys have to plans to fix this issue.

Regards,

Sathish

[Andy Heinzer]

Hi Prasad,

I see that you are trying to use the two dimension gadget in Jira in order to list Versions, but are unexpectedly seeing these duplicate in the gadget.

The reason for this is that the version field is not actually a global field.  Instead versions are a system field that are unique and specific to each project.  It's clear that you have created the same version name in each of these projects, but in the back-end of Jira (the SQL database), each of these versions is different on a for each project.  You can clearly see this yourself with a SQL query such as:

select * from projectversion;

In my example Jira database, I get back results like so:

id project vname description sequence released archived url startdate releasedate
10002 10000 "Version 3.0" NULL 3 NULL NULL NULL NULL NULL
10100 10100 "Version 3.0" 1 NULL NULL NULL NULL NULL NULL

Even though I have two versions called "Version 3.0", these exist in different projects (which have different projectid numbers 10000 and 10100), and technically each version has it's own unique id number.

Given this, I'm not sure how to best suggest condensing this information.  But I at least hope this helps you to understand why Jira is displaying the data there as such.

Please let me know if you have any concerns about this.

Andy

[Prasad Andrews]

Hi @Andy Heinzer ,

Thanks, much for your explanation, I understand but how can I get the report without seeing the duplicates in the gadget.

Is there any other way?

Also, earlier we use Jira v7.9 that time we didn't face this issue now we are using v8.2.5 facing this issue.

[Andy Heinzer]

Hi Prasad,

I tried to recreate this behavior in 8.7.1 first.  And after your last comment, I tried again in both 7.12.3 and 7.9.0.  However in all of these tested versions the behavior of that gadget is identical in terms of how versions across projects are managed in the two dimensional gadget.  They all list versions on a per project basis, none of these merge the versions of the same names across projects.

So I'm not sure how you might have had this working differently in 7.9.0 that might account for the changed behavior here. 

1. Is it possible you were using a different field in the gadget to select upon aside from versions? 
2. Or is it possible the JQL query this gadget is using was previously using a specific project, such as project=xyz in the syntax of the JQL? 

It could be that if you were using some other global custom field that this two dimensional gadget could list all the issues across projects provided they all at least have some value for the custom field there.  OR if the JQL filter being used previously was limiting the results to a single project, that too would only ever show the versions of that project.

I'm not sure how else to explain what you have reported here apart from the gadget being configured to report on a different field.  I can't seem to recreate any means to aggregate this version data within Jira itself.  I am open to the idea that this might be a bug in Jira, but in order to prove that, I'd need to find a version of Jira that operated in a different manner and be able to recreate that behavior there.

It might be possible to use a SQL query to lookup and aggregate this kind of data.  But this would not be something you can easily then see in a dashboard gadget.

Sorry I don't have a better solution here so far, but I'm interested to learn more about how you had this configured in previous versions of Jira that might account for the difference here.

Andy

[Prasad Andrews]

Hi @Andy Heinzer ,

Sorry for the misguided yes I have checked my older version 7.9.2 it's throwing the same error duplicate versioning.

How to fix this issue? Is it Bug in JIRA?

Regards,

Prasad

[Andy Heinzer]

Hi Prasad,

I think I understand why you want the gadget to work in this manner.  But to the best of my knowledge this has never been the way that this works in Jira.  For that reason, I do not see this as a bug. 

I did find an old feature request in JRASERVER-21096 - Cross product version sorting in Issue Navigator.  It seems to touch on the topic of being able to aggregate the versions from all projects that share the same name.

But unfortunately, this was closed with a resolution of "Won't Do".  There is also a note there from one of the product managers that sets an expectation that this request was not popular enough to devote time and effort to work on, and in turn not to expect Atlassian to provide a fix for this. 

I have not found an add-on for Jira Server yet that I think will show what I think you are looking for here either.

Instead, the best I can seem to come up with would be to try to use an Epic burndown to try to see the incomplete issues.  Here is what I tried:

1. Create an issue filter that contains all the issues you want to see here, in my example, it was just

   fixVersion="Version 3.0"

2. Then create a new Scrum board, and choose use existing filter, and choose the filter created in step #1
3. Create an epic somewhere (Let's call it 'myepic1' for example), and then make sure this Epic also has that fixVersion value as the same in JQL filter (Version 3.0)
4. Refresh that board so you can see that Epic in that board now
5. Load the saved filter from step #1, then use the Bulk Edit function on the issue navigator to edit all the issues and add Epic Link of 'myepic1' to all the issues there to add these to the epic
6. From the board created, go to Reporting, and select Epic Burndown.

Ignore the chart here, scroll to the bottom of that report.  This report won't show you completed issue details/numbers, but it will show you all the incomplete issues, and their statuses here.  It's not the same thing as what I think you were looking for here, but it can be helpful as a means to see which issues are still outstanding in that epic, with that version name, regardless of the project they come from.

Other native agile reports won't really be helpful here in my opinion, as the sprint report still segments each version out by the project that version exists in.

Does this help?

Andy

[Paul Howard]

@Andy Heinzer we too would like to see the confluence 2-dimensional array have the sorting capability based on field content (also in our case we're pulling the FixVersion across projects). Not looking to have them combined into a single line, but just sorted next to each other. Said another way, need to list all the "Release 1.0" from the various projects sequentially, then followed by the "Release 1.1".

Example (natural sort): FixVersion : Project

Rel1.0 CSR

Rel1.0 Web

Rel1.1 Web

Rel2.0 CSR

Rel2.0 Web