Trying to Filter Issues with Story Points Not in Fibonacci Series

Jaya Krishna December 7, 2024

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))

 

  • The IS EMPTY condition works perfectly and retrieves issues with no Story Points set.
  • However, the NOT IN (1, 2, 3, 5, 8, 13) part is not working. No issues are fetched, even though I have test issues with invalid points

I’m trying to achieve:

  1. Identify issues where Story Points are either empty or not one of the valid Fibonacci values: 1, 2, 3, 5, 8, 13.
  2. Use this query to filter issues in Jira Automation for further actions.

Could this be related to how Jira handles numeric fields in JQL? Any help would be greatly appreciated!

2 answers

2 votes
Tomislav Tobijas _Koios_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 7, 2024

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).

2024-12-08_08-26-35.png

Can you maybe share the exact JQL you're using or a screenshot of your screen?

Cheers,
Tom

David Nickell
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 7, 2024

you beat me by 20 seconds...    I recommend looking at other conditions of the JQL as being the problem

story points.jpg

Jaya Krishna December 7, 2024

Hi,

This is the query I'm Using: 
Here 1 is a valid still its fetching it in query:image.png


And second bug has invalid Story Points:
image.png


So If I run NOT IN operator part separately second bug should be fetched but this is the result no result:
image.png


In your case are you able to see any invalid story points issue fetched.

Thank You.

Tomislav Tobijas _Koios_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 8, 2024

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.

2024-12-08_09-07-27.png

Here's how these two different fields look in the issue view screen:

2024-12-08_09-11-45.png

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

Jaya Krishna December 8, 2024

Hi @Tomislav Tobijas _Koios_ , @David Nickell 

Understood, That helps, I tried with Story Points now please check:

WhatsApp Image 2024-12-08 at 1.52.14 PM.jpegWhatsApp Image 2024-12-08 at 1.52.15 PM.jpeg


I do have issues that have invalid story points, with status correct status.

David Nickell
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 8, 2024

I don't quite follow but here's some old school wisdom....

  • Comparing to EMPTY (null) can always be tricky. 
  • If your value doesn't exist, its ignored in a not in test.  Null is truly not testable other than to say "is" or "is not" null (Empty)
  • in your query, the NOT IN Clause may be getting distributed further in your formula than you think.  
  • it seems like each of your conditions can be standalone.  Add more parenthesis..  (Project = x) AND (Status = y)  AND (story points not in (3,3,3,))  etc

I'll be signing off shortly -- good luck!

 

Tomislav Tobijas _Koios_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 8, 2024

@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

1 vote
David Nickell
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 8, 2024

Your test in JQL is for Story Points.   The field you highlighted is Story Point Estimates

Hopefully this resolves it :-) 

Points V Estimates.jpg

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events