Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,473
Community Members
 
Community Events
176
Community Groups

JQL to find an empty mandatory field?

Hi folks,

I've recently added a mandatory custom field, and then done a bulk update to set it to one of two values, based on another field (a label, which we're finding too error-prone).

The bulk updates worked okay, but there were some exceptions, ie tickets that didn't match the bulk update criteria, and therefore the mandatory field is not set. I want to mop these up.

When I try to use JQL to find these, Jira just tells me there aren't any. Yet I can go through the backlog and pick them out. So what's occurring?

My query is this:

project = TLA and (field != "Option 1" and field != "Option 2") OR field is empty

 

This only finds records where I've actively set field to a valid value that isn't "Option 1" or "Option 2." It's refusing to match "empty" with "not set." How do I find the records that haven't been captured by the bulk change?

1 answer

Hi @Jim Strange 

Are you sure the issues dont have a value? Issues that dont have the field in their view screen might still have a value even though you cant see it on the issue :)

Hi Mathis,

It's a brand new field so the values will have defaulted to Not Set. There are only three possible options for this field and I've tried them all!

Hmm.. what happens if you pick one out and change the value from None to whatever and then back? Are you able to query them then?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events