Community moderators have prevented the ability to post new answers.
It is not going to. As I already said, the axes fields must be countable, and text fields are NOT countable. Even if you coded to make them appear, you'd rarely get a result other than "1". Take this question as an example - each answer and comment is a text field. Unless someone posted exactly the same comment repeatedly, you've only got 1 of each.
As Keith has pointed out, the only useful one that's missing is cascading selects. Text, numbers, date/time, all produce nonsense if you could use them in this gadget.
Hmm, someone just posted "this is a bad biased assumption" and voted me down I'm curious to know why. I'm interested in a use case for text - just because I can't think of anything even remotely useful (in the context of a counter gadget), doesn't mean there isn't one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the use case for text :
- user want the ability to enter arbitrary value to an issue.
- user want the ability to make 2dimensional statistic with this arbitrary value.
it mainly depend on the context and customers needs , arguing with uselfuness with customers is another story ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nope. Utterly useless. Arbitrary text is the whole point - it's mostly, if not entirely countless, and hence useless as a statable object.
This is not a case of arguing usefulness with a customer, it would be negligent to point out that they are trying to do something dumb.
On the other hand, I left out "labels". They should be statable too...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
'pointing out that they are trying to do something dumb' is a different story ..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Use case: We automatically populate a text field with an email address from an external database based a selected field in a parent issue when sub-task is created. It's a text field but since we control the input it is standardized and we'd like to be able to report on it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's still a text field and hence arbitrary - it can't know that the values are fixed. You could swap it to a select list as you know what the inputs are.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes I know. The list is controlled by an external system though and has a huge number of emails and is regularly updated. This isn't a big deal but I thought I'd give you an actual use case =)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use this plugin
it add statistic for Custom Field Types :
best regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Anyone making the biased assumption that one use case must fit all use case is wrong .
It all depend on the context, but there is more than exctly one way.. ;)
Regarding the original question,
You can use this plugin
it add statistic for Custom Field Types :
best regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seems that Dashboard widgets like 2D Filter only allow selecting certain field types, per https://confluence.atlassian.com/display/JIRA/Adding+the+Two-Dimensional+Filter+Statistics+Gadget:
"If choosing a custom field, please note that the following types of custom fields are supported by this gadget out-of-the-box: 'Group picker', 'Multi select', 'User picker', 'Select list' and 'Version picker'."
In particular, note that per https://jira.atlassian.com/browse/JRA-6411, Cascading Selects are also noteworthy for not being selectable (without workarounds).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Re-indexing only needs doing if you've been inserting data. New fields will show as soon as they're added.
However, for fields to be shown in the Axes drop-down, they must be "statable" - that is, things that can be counted. If you've added text, number or date fields, they'll never appear. Select list types and users will be,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic & Keith,
I have created free text cutomfield and assiciated with project, but this custom field is not showing in two diemntional filter statics gadest.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nic,
I face some issues . I have 2 label fields
One label field is vaiable in the drop-down of Two dimensional gadget but the other field not listing.
What could be the reason?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What type of fields are they? Two label type fields works here for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Both fields are label fields. Techncally it should work.
I have many Labels fields. There is no poblem with other Label fields.
But few of them not working.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok. Can you check that the fields have "searchers" in their definition (it's under custom fields -> field -> edit)
If they do, then the next thing is to start looking at logs, I'd expect to see errors when your user clicks on "edit" on the gadget to get the config screen to try to select the labels as axes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the only useful one that's missing is cascading selects. Text, numbers, date/time, all produce nonsense if you could use them in this gadget.
this is a bad biased assumption.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
after changing the search template for your custom field you need to perform a reindex , please refer to jira-stattable-searchers wiki and https://bitbucket.org/treymarc/jira-stattable-searchers/issues/13
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you! but to what template should I change for number field to display in two-dimensional
I did re-index too but didn't see any this field in two-dimensional
Screen Shot 2017-03-07 at 2.29.17 PM.png
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try changing it to "numeric (stats)" - that's the "searcher" that Marc's add-on adds. (And re-index again, I'm afraid - not a lot we can do about the JIRA architecture here, however clever the code)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
if you created those custom fields then do reindex !!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.