You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are using JIRA next-gen and have added a custom field (called Affected version) for defects. The problem is, when I query for records without a value, it returns ALL the issues!
The query is simple: project = "CC" AND Type = Defect AND "Affected Version[Labels]" is EMPTY ORDER BY created DESC
I've done this many times in JIRA Server, so I'm very confused. Why is it doing this?
Hi @Arlan LaVoie -- Welcome to the Atlassian Community!
You note adding a custom field called Affected Version. What is the field type for that one?
There is already a built-in field called affectedVersion. What is the need for a new field?
If your new field is a text type, there is definitely an existing/open defect for IS EMPTY not working if the field has *ever* had a value before. (Atlassian is working on fixing that one...) If that fits your use case, you could try this:
project = "CC"
AND Type = Defect
AND "Affected Version[Labels]" = ""
ORDER BY created DESC
After some backlog checking, I wonder if you are facing this issue related to project-level custom fields: https://jira.atlassian.com/browse/JRACLOUD-76482
If so, the work-around is to use the custom field number rather than the name in the query. Please let me know if that helps you. Thanks!
You could ask your site admin for it, or quickly call the REST API. Here's how to do that:
Well, that is unfortunate. At this point I am unclear what else to try. If you are on a paid-instance of Jira (Standard or Premier, not Free), I recommend asking your site admin to submit an incident to Atlassian here: https://support.atlassian.com/contact/#/
You have enough diagnosis steps and have tried their work-arounds, so perhaps they can see something in your instance that we are missing.
Once you hear back from them, please consider posting back here so the community can learn too. Thanks!