Hello all,
I am trying to validate a query that I am trying to build, and not sure it's correct. I am trying to query all tickets that moved to "status x" during a period. So what I've used is
Project = my project AND status changed to ("status x") during (date, date)
Is this correct use? I am not sure the "changed to" works as it is expected to. Any help would be appreaciated!
Thanks,
Nik
The most similar way that I know is the "WAS" flag. Example
Project = "PJTKEY" AND status WAS "Backlog" during ("2022/10/19 10:00", "2022/10/18 10:00")
The query above returns all issues from project "PJTKEY" where status WAS "Backlog" between 19/10/2022 10:00 AM and 18/10/2022 10:00 AM.
The time is optional, you could discard from query
That was my original thinking but in a Kanban world, that would skew the numbers as some tickets might already be in that column. Anyhow, I found a way to validate my query and it works fine! Thanks for the quick response anyway @Rafael Costa !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The operator CHANGED TO should work for that: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/#Advancedsearchingoperatorsreference-CHANGEDCHANGED
To check your results perhaps narrow the window of time as an experiment (e.g. a few hours) and then look at the resulting issues change history to confirm the results.
If it is not working, what is not happening as you expect?
Update: Are you using a team-managed project for this query? If so, there is a known defect for the CHANGED operator for that type of project: https://jira.atlassian.com/browse/JRACLOUD-78387 and the work-around is to use the status ID value.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.