I want to add"Text Field" type Custom field to "Statistics Type" in Workload Pie Chart how to add ??

[Kumar]

We have a custom field called "AIERulename" its a Text Field. I want to add it to "Statistics Type" in pie chart. when I'm trying to add its not showing the Text Filed type Custom Fields in the Statistics Type dropdown list. Here each Tickets have a different "AIERuleNames" some times will use the similar name depends upon  ticket. Here If I add this field to the Pie chart gadget so that i can see the report how many ticket created per month with similar AIERuleName  

Can any one suggest me regards this.

Thanks,

Phani

[Josh Steckler]

Hi Kumar,

Pie charts can only be used with non-text custom fields.

[Kumar]

Hi @josh  Thanks for your response is there any other way to use the Text Fields in the Pie chart Gadgets by using like any add-on's ?? 

[Nic Brough -Adaptavist-]

Not reliably, there was one add-on that allowed it, sort of, but it's always caused problems when the data sets get large.

It's really not that useful either - text is not something you should be building pi-charts against, as each text could be different, so you'd just end up with a chart made up of lots of single-point slices.

[Kumar]

Hi @Nic Brough -Adaptavist- can you tell me that add-on will try that once

Thanks,

Kumar

[Kumar]

HI @Nic Brough -Adaptavist- Is this add-on that you have suggested 

https://marketplace.atlassian.com/apps/1211529/stattable-searchers?hosting=server&tab=pricing

I have installed this add-on is there any problem with is add-on if i install is this add-on cause any error for my application can you please suggest regards add-on is it safe or not 

because its supporting the TextFields custom fields in pieChart gadget

thanks, 

[Nic Brough -Adaptavist-]

Yes, that's the one I have had to remove from several Jira installations to fix their performance issues.

[Kumar]

Hi @Nic Brough -Adaptavist- what kind of errors it causes mainly so after I installed. After few min while i'm testing that add-on my jira  once in a while it runs  slowly some times it takes some time to load . Is that error because of that add-on.

To avoid the errors causes from this add-on can you suggest any thing 

Thanks, 

[Josh Steckler]

The best thing to do would be to switch to a non-text custom field for the AIERulename if you can.

[Nic Brough -Adaptavist-]

The problem is not "errors" in the add-on, but "errors in what you're doing". 

Text fields are not suitable for gathering together like this because they are text.  The add-on is having to do a vast amount of work to build a false equivalence and find the odd potentially matching blocks of text over a range of data that is very time-consuming to process.

The add-on itself is doing what it can.  But you're asking it to do something which is intensive on processing and hence causes significant load.

My only suggestion is "don't try to abuse text fields like this".  Get rid of the add-on, and move to using a list field, as that's what they're for.

[Kumar]

Hi @josh @Nic Brough -Adaptavist- Thanks for your response and i will go with List field the thing is my user are demanding that they must required that particular field in that pie-chat that the problem so I will follow your Suggestion and I will create a List field and will use that.

One more thing can you please give a suggestions on this too please 

click: https://community.atlassian.com/t5/Jira-questions/Only-Particular-group-selected-In-field-in-ticket-have-to-notify/qaq-p/923852

That would helps me a lot

Thanks, 

Kumar

[Kumar]

Hi @Nic Brough -Adaptavist- I have a small Doubt regards this issue I just want to clarify it That's it. 

Here is the Thing

 In my AIERuleName(Text Field) what actually it does means we will use that field as to enter the "What Type Of Ticket and we will enter that Ticket Name in that field"  in my project we have like as of now 80-90 different Types of ticket  Names that will generate every day. New Type and most of the Time We will use the Same Type Name to create  Ticket . So, i want the take out the report depends on Ticket Names so that's the reason i need to add this "Text Field" in the Pie-Chart Gadget.

Here By using that plugin I'm adding that particular field only  In the pie-chart  it will displaying all the "Types of ticket" That i have in my project .

As You suggested to use the Custom Field "Select List Field" Type. In that i will add all the Types Of the Ticket Names that i have available as of now. Here If i add that "Selected List Field" in the pie-chart it will also shows the All the different Type of Named Ticket  that i entered in the Selected List. It will appear in the Pie-Chart Gadget. 

we will use the Automation to create tickets in my project through Phantom. For auto created tickets There is no problem by adding Selected list custom field.

But the thing is for Manually created ticket there is a problem with Selected Field when they click on drop-down List button it will display all the 80-90 types values its very difficult to selecting the option form the list while creating manually   In future it may increase more Values.

I just want to know In my case  by adding the Select List and Text field that we are using does the same thing I want to know the Difference That's it @Nic Brough -Adaptavist- 

Can you please guide me regards this so that I can learn it would me helps me .

Thanks,

Phani

[Nic Brough -Adaptavist-]

Ok, this still means you are not using the right type of field though.  The AIERule field needs to be a select list for your reporting, not a text field.

[Kumar]

Hi @Nic Brough -Adaptavist- thanks for your responce.

The only thing i need to know is you said if i use the text field for reporting its causes the error and also you mention that you have tried this kind of issue and you faced some errors and you uninstalled that add-on to get rid of it.

So, in my case if created Selected list and add those all the 90 values  in that field and add that field in the pie-chart gadget does it cause the any problem???

because in my case if i add the text field or select field  in the pie-chart doing the same function there i got stuck.

[Nic Brough -Adaptavist-]

Yes, I already explained that above.  90 values in a select list does not have a problem, other than being a bit of a pain for users to find the right one.

[Kumar]

Hi @Nic Brough -Adaptavist- Now I understand I'm forcing the pie-chart Gadget to give report  by using "Text field" by using the Add-On which it not support . So, if I force to do that it causes the performance issue in jira right. 

Thanks Nic for you suggestion and also can you please suggest regards this new issue that i have please go through this link

https://community.atlassian.com/t5/Jira-questions/Only-Particular-group-selected-In-field-in-ticket-have-to-notify/qaq-p/923852

Thanks,

phani

[Robert Horan]

I don't mean to be the contrarian, but I have to disagree with the sentiment that It's really not that useful - while text fields are not the ideal format for building pie charts, sometimes that's all you have.  Converting from a text to a select field is not an option.  

"But you should have thought about that before..." Lemme stop anyone before that gets posted so I can introduce my frenemy named reality.

[Nic Brough -Adaptavist-]

But a text-field based pie chart cannot do anything other than "one slice per issue".  By definition, every chunk of text is different.  I don't see any use for a pie chart with that.

[Robert Horan]

I wouldn't say every chunk is different.  Every chunk is potentially different.  However, consider this scenario.  A user needs to categorize a series of issues, and does not want to use labels, because labels already has information.  They also are not an admin and they have a field available that is not in use. 

So they bulk edit several batches of issues, adding a single word to each batch.  This ensures that all of the issues edited have consistent results. 

[Nic Brough -Adaptavist-]

No, every entry that goes into a text field has to be treated as different, it doesn't matter if the data in one is the same as another, the system has to assume that they are different items.

Your user is botching around a labelling problem here.  They should be using labels for this.

[Robert Horan]

So then this is an inability of the system to be able to identify identical strings. 

I get your point but again, Labels CANNOT be used here because there is are irrelevant (to this use case) labels applied to these issues and making a new field is not an option as my user (and I) does not have admin rights on this instance.

[Nic Brough -Adaptavist-]

It's not a failure of the system to do something with a data type that is not for the type of data you're using it for.  It's a failure of your humans, they're bludgeoning a "fix" into something that's the wrong place for it.

[Robert Horan]

I edited my reply - and I assure you I'm not trying to be stubborn for no reason.  Failure was not the right word, and again, I understand your point but some flexibility here would be EXTREMELY beneficial, if not in how pie slices work then in the ability for project admins to add select fields to their own projects without having to go to an admin.

As admins, it's very easy for us (though I am not an admin in this instance) to see the reasons for restrictions, but for users that have to be resourceful with the tools they have at hand, it can be extremely frustrating.  Sometimes bludgeoning in a workaround is the ONLY solution, because there is no way to get things done otherwise without an admin - who may be unavailable or unwilling to assist.

If there was a way to only include certain labels or exclude others in the pie chart this would be a non-issue.

[Nic Brough -Adaptavist-]

I've pointed in the wrong direction as well.  The failure is in your admins not meeting the needs of the people using the project.  People shouldn't need to be "resourceful" in order to use a tool that can already do what they want.

For the pie chart include/exclude - yes, I can see how it lets us down when you have multiple-selection fields.  For single selects, it's ok though, you can just use filters with "my-select-field in (a, b, c)" and it'll only show those three.

[Robert Horan]

If only the single select could be used :(

The worst part is there is a single select field in this case with MOST (but not all) of the options this person needs.