Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Filter Issue when trying to compare Story Points to Original Story Points

Coady Krzysztof January 30, 2025

Hi all,

 

 

 

 

I created an automation rule to populate the Original Story Points field with what is entered into the Story Points field.  I also created an automation to send me an email when the Story Points field has been changed and no longer matches what is in the Original Story Points Field.  This is working fine.

My issue is I am trying to create a filter that will show me all the cases where the Story Points field no longer matches the Original Story Points field (either greater or smaller number). I am getting this an error, and I have tried switching the order of the Original Story Points field and the Story Points field. This is the JQL I am using and the error I get.

project = "My Project" AND status = "To Do" AND "Story Points[Number]" != "Original Story Points[Number]"

Value 'Original Story Points[Number]' for the 'Story Points[Number]' field is not a valid number.

I am new to writing JQL so any help would be appreciated. Thanks CLK

2 answers

1 accepted

2 votes
Answer accepted
Bill Sheboy
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.
January 30, 2025

Hi @Coady Krzysztof -- Welcome to the Atlassian Community!

The built-in features of JQL do not support comparing fields.  It is an issue search language and not an actual SQL.

The possible workarounds for this depend upon how often you need this capability and willingness to spend money / time:

  • need it one time
    • Export the issues with both fields and use spreadsheet functions to compare them
  • need it often
    • have money to spend
      • Investigate the Atlassian Marketplace for addons / apps which add such features to JQL
    • have time to spend
      • Create an automation rule, triggered on changes to either field, which compares them and adds an indicator which could be checked with JQL (e.g., a label)...or
      • Create an automation rule for a specific event (e.g., sprint completed) which reports on any differences in the fields found

Kind regards,
Bill

Coady Krzysztof January 30, 2025

Wow, thank you so much it worked.   My first post and success!

I modified the automation rule that I made that emails me when the Story Points no longer match the Original Story Points to also populate the Approved By field with my name. Created a filter to show me all the cases where the Approved By field is not empty.  

Thank you again. 

Like Bill Sheboy likes this
0 votes
Petru Simion _Simitech Ltd__
Atlassian Partner
January 30, 2025

Just realized the solution is already provided.

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events