Forums

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

Hi All, I wanted JQL, to search issues whose fixversion , once set, is not changed in later point

Mathurashish Kumar, Sant June 9, 2024

to search issues whose fixversion , once set, is not changed in later point of time. 
Example: If a Type= Test is set with a fixversion as 2024.M.Release, It fixversion is set and later its not changed .

I was trying the below mentioned Query
issuetype = Test AND "Test Category" in (Functional,Nonfunctional,Security) and created >2024-03-29 and fixVersion =2024.M.Release and (fixVersion is not EMPTY AND fixVersion was not changed)

 

1 answer

1 vote
Sudarsana G
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.
June 10, 2024

Your attempt at crafting the JQL query to search for issues whose fixVersion remains unchanged once set is on the right track. However, Jira's native JQL does not have a direct function to track changes to a field over time within the same query. You may need to leverage a plugin like Jira Misc Workflow Extensions (JMWE) or ScriptRunner to achieve this level of granularity.

Here's an example of what the JQL query might look like with ScriptRunner (assuming you have a scripted field called Original FixVersion that stores the initial value of the fixVersion):

issuetype = Test AND "Test Category" in (Functional, Nonfunctional, Security) AND created > "2024-03-29" AND fixVersion = "2024.M.Release" AND "Original FixVersion" = "2024.M.Release"

Mathurashish Kumar, Sant June 10, 2024

Hi @Sudarsana G ,

Thanks for reply.

Currently we dont have filed called "Original Fixversion". I can check with my team on this. Thanks for Suggestion.

My Query to above example is:

Suppose original Fixversion was 2024.M.Release and Current Fixversionis Also 2024.M Relase. If there was changes in between like 2024.S.Release and after 3 weeks it was reverted back to 2024M.Release, Then above query will not be able fetch correct data.(Correct me, If I am Wrong)

My Question was, Original and Current will be same and no other fixversion was used.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events