How do I add a Custom Number Field and "Issue Key" field to a Gadget X/YAxis pickers?

[Nir Damari]

Mostly Title, I followed this guide https://confluence.atlassian.com/jirakb/story-key-and-its-linked-bugs-count-in-a-dashboard-gadget-1102612555.html and In the last section I was requested to create a Two Dimensional Filter Statistics gadget and select "Key" and "Linked bug count" field to the X/YAxis, but I can't find them :(
Is there a way to add them back?

To explain this better my desire is to create a Widget inside our Developers dashboard per their request to show them each Story that was related to them on Y Side and Bug Counter per Story that was related to it with "is caused by" and "Causes" relation between Story and Bugs.

The idea at the end is that the dashboard would show
Key-10001 | 5
Key-10002 | 4

If he clicks on the 4 or 5 he is redirected to the query that shows him those bugs related to this Story.

Is there a way to do it?

Even with the guide above the Bug Counter is not counting per story but it counts all bugs with "is caused by"

[Bill Sheboy · Accepted solution]

Hi @Nir Damari -- Welcome to the Atlassian Community!

Based on what that article describes, it is trying to use an automation rule to set a number field with a counter.

I do not believe there are any built-in dashboard gadgets which can show issue keys and a custom number field...with a link to the counted issues.  Instead many of them show counts of things from select list fields, not numbers.  You could either change to use a select list field or investigate marketplace addons which have such gadgets.

For your last question about the counter accuracy, I suspect there is either a rule problem or a difference in the original article's approach an your scenario.  If you post your complete rule image, along with details of the actions and audit log details, the community can help to improve the rule.

Kind regards,
Bill

[Nir Damari]

Hey @Bill Sheboy 

Thank you for your time, You are right an addon is the only way to create this, apparently it not out of the box by jira.

Best Regards,
Nir