Pie Chart Gadget Corrupts JQL with "Non-Standard" Custom Field on Production, but Works on Test - Wh

[MidnightExe]

Hi Community,

I'm facing a very strange issue with a Pie Chart gadget that behaves differently on our production and test servers, despite what appears to be an identical configuration. I'm hoping someone might have an idea what the hidden difference could be.

-

The Goal: We want to create a Pie Chart based on a saved JQL filter. The chart should be grouped by a specific custom field named 'OE / Division' using the "Statistic Type" setting in the gadget's configuration.

The Problem on our Production Server: The chart shows an extra bar with the name 'Irrelevant'. (screenshot below*) And the bar on testsystem is not showing --> thats  how it's supposed to look.

This is the jql query:

project = DEM AND issuetype = Demand AND status in (Backlog, Planning, Analysis, Deployment, "In Definition", Refinement, Conception, Realization) ORDER BY id ASC

After uploading a pie chart and clicking on total issues the query changes automatically to this one and it says: Error in the JQL Query: A field name cannot be empty. (line 1, character 156)

project = DEM AND issuetype = Demand AND status in (Backlog, Planning, Analysis, Deployment, "In Definition", Refinement, Conception, Realization) AND NOT "" is EMPTY ORDER BY id ASC

The custom field shows the following information: “This custom field stores its data in a non-standard way, that's why we can't show accurate data about its values or issues using it.”

(same info text on test and production system)

this is the Select List (cascading) custom field config with some options:

The Mystery on our Test Server: Here's the strange part: Our test server is a clone of our production environment. We replicated the exact same setup there:

1. The custom field 'OE / Division' shows the same "non-standard" warning in the admin backend.

2. The JQL filter in the gadget's configuration also shows the same syntax error warning.

3. However, on the test server, the Pie Chart gadget renders correctly and displays the data exactly as we need it! 

What We've Checked So Far:

Jira & App Versions and Gadget & Filter Configuration

*Screenshots:

It should look like this (this is our testsystem)

But it looks like this (this is the production system)

Any ideas or suggestions on what to investigate next would be greatly appreciated!

Thank you!

[Zahrah000]

This looks like one of those cases where the issue isn’t with the gadget config itself but with how production is handling the custom field data. Since the JQL gets rewritten to AND NOT "" is EMPTY, it’s often a sign of either indexing problems or some “orphaned” values in that cascading field.

I’d suggest running a full re-index on production and also checking if the field context/options are 100% identical across prod and test. Sometimes deleted or malformed options linger in production data and show up as “Irrelevant” in gadgets. If the re-index doesn’t clear it, compare logs between environments or test a JQL like "OE / Division" is EMPTY to see how it behaves.

[MidnightExe]

Thanks for the info, will try the full re-index option. 

[Marc - Devoteam]

Hi @MidnightExe 

You mention uploading a Pie Chart, are you using the default ootb Pie Chart gadget or are you using an app?

Can you show the Pie chart configurations?

Have you checked the cascading select field, do they have the same options?

Is the context set for the correct work items and projects, and differences?

[MidnightExe]

Im talking about the standard pie chart by Atlassian. I have checked every single option in the fields option. Everything is set the same. Will try to run a full re-index.

[Marc - Devoteam]

Hi @MidnightExe 

Did a full re-index solve the issue?