Gadget Total Unique Issue count hyperlink gives error

Ranganath HV September 11, 2017

Two dimension report total count gives filter=null

When used two dimensional gadget, Total Unique Issues - Total count will give null value, but open with all issues when clicked on view in JIRA.

Hyperlink of Total Unique Issues gives null value. 

HyperlinkError.jpg

2 answers

0 votes
Alex Dopp May 12, 2021

It is 2021 and this is still not resolved.

I found the following bugs for server, but this is present in cloud too. Anyone have the respective cloud bugs?

https://jira.atlassian.com/browse/CONFSERVER-53028

https://jira.atlassian.com/browse/CONFSERVER-41038

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 11, 2017

What version of JIRA are you using?  

Is this by chance being viewed through a Confluence page?   Just curious why we have a 'View in JIRA' link if we're actually viewing the JIRA dashboard directly.  

There were some older bugs that changed the behavior of this dashboard gadget, but I believe this has been fixed since JIRA Server 6.3.12 and later revisions per https://jira.atlassian.com/browse/JRASERVER-40713

Ranganath HV September 14, 2017

I am using JIRA v7.2.6

Yes, I am viewing this through confluence page. From Confluence page if you click on 'View in JIRA', it navigates to all 78 issues. This should happen when you click on total count "78"

Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 14, 2017

Thanks for that information, I didn't realize this was in the Confluence view.   With that information, I was able to recreate this problem.  This is actually already a documented bug in Confluence.  Please see https://jira.atlassian.com/browse/CONFSERVER-41038 for details.

This bug is in the confluence project because this only appears to happen when using the JIRA Macro in confluence to render this chart/gadget.  That same chart renders correctly when viewed in the JIRA dashboard.  So this is something that will likely need to be fixed in the Confluence code base.  Sorry there is not a clear fix for this yet, but I would suggest to vote on and watch that ticket for updates on this problem.

Suggest an answer

Log in or Sign up to answer