Perhaps being able to query issues in open or closed sprints will suffice?
I want to know how to do this as well. My reasons are that I want to know how many tickets I've completed in another project during my Sprint's start and end dates. Something like:
project="Kanban" AND status was Resolved by currentUser() and resolved >= SprintXYX.startDate and resolved <= SprintXYX.endDate
But that query won't exclude tickets that were resolved before the sprint started. I think what Truong (and everyone else on this thread) wants to be able to query:
resolution is not EMPTY and resolution was EMPTY before startofOpenSprints()
Obviously, the above query doesn't exist since startofOpenSprints() is not a real queryable date field.
However, if you time it right, right before you close your sprint (if your sprint is 14 days long), run this JQL:
resolution is not EMPTY and resolution was EMPTY BEFORE -14d and Sprint in openSprints()
you can search for 'sprint' in the returned response -
CTRL+F search for sprint - you may get the field which lists down 'sprint details' - ours is a custom_field with some ID, so in jql you can then filter using that field id - or just pull out data from the returned response , accessing dictionary and key as custom field ID
JQL search can be like - jiraURL/jira/rest/api/2/search?jql=Sprint='sprint_name'&fields=customfield_100&maxResults=400
As far as I know, there is unfortunately no term for this in pure JQL.
My personal goal is to monitor if any tickets have been created and moved into an active Sprint without my knowledge (alarm!). I currently work around the missing JQL term by using startofWeek(). Since all our Sprints start on (the same) Monday I use this query:
sprint in openSprints() AND createdDate > startOfWeek() ORDER BY createdDate DESC
By this I get all the tickets which have been created since start of Sprint, but only for week 1. In week two I only get the tickets for week 2 and lose all from week 1 (which is OK for me since I try to react instantly). I put the results of the query on a personal Jira dashboard and check them multiple times a day.
I hope this helps anyone who has a similar usecase.
This workaround didn't help me because I don't just need tickets created and moved into the sprint, but even existing tickets moved into the sprint. Like you, I want those highlighted on a dashboard. I ended up having to use the Jira API to do it. From Python, I made an API call for all issues in that sprint of the right type, and once in Python, I could access the issue changelog to see when it was moved into the sprint. If that date was after the sprint start date, bingo!
Later I added code to put the label "ScopeAddition" on the issue after it's identified as being added after the start of the sprint. Then my dashboard just looks for that label.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events