Been researching how to find issues when they are updated at a certain point and I think i got it, But before I walk away. I am looking for the reverse.
As a Scrum master I need to find all stories of a certain size that have started to age and need updating or closing.
Here is what I came up with.
Project = ABC AND issuetype = Story AND "Story Points" = 5 AND in Sprint in openSprints() AND updated > -6d
if I understand this correctly the query will find all stories in project ABC that 5 points in size in the open sprint and has not been updated in more than 6 days.
The meaning of updated to me as I understand it is a Status change from Open to In Progress , as an example. Did I interpret the query correctly?
Checking the field updated, you are checking for any changes, not just status. If you want to limit the search to specific status changes, please try:
project = myProject AND issuetype = Story AND "Story Points" = 5 AND sprint IN openSprints() AND status CHANGED FROM "Open" TO "In Progress" BEFORE -6d
Please note this works well if you only have Classic projects. If you have any Next-Gen projects, the status change functions produce unreliable results. Here is the defect for that issue:
https://jira.atlassian.com/browse/JRACLOUD-70797
And here is some documentation on the advanced JQL functions:
https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/
https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/
Best regards,
Bill
By the way @Thomas Cucolo ,
updated > -6d
means the update date is in the last 6 days, so that returns the issues that WERE updated in the last six days.
If you want the issues that WERE NOT updated in the last six days, the JQL clause should be
updated < -6d
The same applies for the status change query that @Bill Sheboy gave. If you are looking for the ones that were updated more than six days ago, you should be using
BEFORE -6d
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, @Emre Toptancı _OBSS_ for correcting my error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you very much for the clarification I knew something was off I appreciate both @Bill Sheboy and @Emre Toptancı _OBSS_ for the assistance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join us to learn how your team can stay fully engaged in meetings without worrying about writing everything down. Dive into Loom's newest feature, Loom AI for meetings, which automatically takes notes and tracks action items.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.