Jira Two Dimensionnal Filter - Custom field missing

Michel Marcoux November 18, 2012

I've create a custom field (number field) and I try to add it in a Two Dimensionnal Gadget under X Axis, but my custom field is not in the list of available fields there to choose from. Why that?

5 answers

1 accepted

1 vote
Answer accepted
Theinvisibleman
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 19, 2012

Hi,

As Jobin said, only certain custom fields are supported by the Two Dimensional Filter. These are : 'Group picker', 'Multi select', 'User picker', 'Select list' and 'Version picker'.

You can view the documentation about this gadget here : https://confluence.atlassian.com/display/JIRA/Adding+the+Two-Dimensional+Filter+Statistics+Gadget

Cheers,

Joe

0 votes
jose_castro June 9, 2016

Hello folks. I know this is an older post. However I just wanted to make you aware that I opened a feature request for the documentation to be updated https://jira.atlassian.com/browse/JSW-13785 as well as the ability to search instead of drop down when you are selecting fields https://jira.atlassian.com/browse/JSW-13786 for the gadget statistical parameters.

0 votes
Joseph Bettio April 2, 2015

Thanks for the responses everyone, I was able to get the issue resolved by changing field type. 

0 votes
sundar paul October 23, 2013

We are using 5.0 jira version, we have added Cascading Select custom filed. Cascading Select filed is not seen in any gadgets as x or y axis. Is there any work around to put my Cascading Select values in my jira dashboard.

0 votes
Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 19, 2012

Only certain custom field types are available for that gadget. Ones like Select list for which statistics can be generated. Custom fields of type Number field etc wouldn't be available.

The searcher should implement CustomFieldStattable interface for the field to appear.

Suggest an answer

Log in or Sign up to answer