I'm trying to identify issues where Story Points are either empty or have invalid values using the following JQL:
("Story Points" IS EMPTY OR "Story Points" NOT IN (1, 2, 3, 5, 8, 13))
I’m trying to achieve:
Could this be related to how Jira handles numeric fields in JQL? Any help would be greatly appreciated!
Hi @Jaya Krishna ,
Interesting to hear that this doesn't work for you. I've just tested it and it works as expected - filters out all issues where "Story Points" is empty or where Story Points value is not in the defined array/list).
Can you maybe share the exact JQL you're using or a screenshot of your screen?
Cheers,
Tom
you beat me by 20 seconds... I recommend looking at other conditions of the JQL as being the problem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
This is the query I'm Using:
Here 1 is a valid still its fetching it in query:
And second bug has invalid Story Points:
So If I run NOT IN operator part separately second bug should be fetched but this is the result no result:
In your case are you able to see any invalid story points issue fetched.
Thank You.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jaya Krishna ,
One note here - you're actually talking about two different fields here.
On the issue screen, you have Story point estimate and in the filter/JQL you're using Story Points.
Here's how these two different fields look in the issue view screen:
So, you could either configure the issue layout to have/use Story Points instead of Story point estimate, OR adjust JQL to use "Story point estimate" instead of "Story Points".
Mind trying some of these things and let us know how it goes?
Cheers,
Tom
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Tomislav Tobijas _Koios_ , @David Nickell
Understood, That helps, I tried with Story Points now please check:
I do have issues that have invalid story points, with status correct status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't quite follow but here's some old school wisdom....
I'll be signing off shortly -- good luck!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jaya Krishna but did you add Story Points field to the issue layout and add values to the issues?
From the first image, I can see that all visible issues don't have values for "Story Points" and therefore second JQL will not return any results if you don't add:
("Story Points[Number]" IS EMPTY OR "Story Points[Number]" NOT IN (1, 2, 3, 5, 8, 13))
Regardless of that, in case you're still using existing values of Story point estimate field, I would suggest trying the following query: 👇
project IN (10057) AND issuetype IN (Story, Task, Bug) AND status NOT IN (Backlog, Discard, Done) AND ("Story point estimate" IS EMPTY OR "Story point estimate" NOT IN (1, 2, 3, 5, 8, 13))
As @David Nickell already said, I've removed some parenthesis as they are not necessary.
Cheers,
Tom
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your test in JQL is for Story Points. The field you highlighted is Story Point Estimates
Hopefully this resolves it :-)
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.