Forums

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

JQL to search for issues added to sprint at date

ConflictGK
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 3, 2019

I'm trying to build a jql in order to get the list of issues added on sprint backlog at a given date. This info is available in web application by visiting the burndown chart on jira. There is a log below the figure listing all the events and associated issues. 

Until now, I have only managed to retrieve only the issues created at specific date by using created jql function. 

For example if I search for:

sprint={sprintId} and created>={date} and created<{date+1}

the results list all the issues created that specific date but not issues that were already existing previously and were moved to the sprint backlog.  Thanks

1 answer

0 votes
Alexander Bondarev
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.
April 3, 2019

Hi. 

i know that ScriptRunner has usefull JQLs - like checking issues that were added after the sprint started.

maybe it helps you

Marcus Pereira
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 17, 2020

As far as I know, it will not. These functions tell when something is added considering the start date of the Sprint, but not when the issue was added to a certain Sprint. Honestly, I am having the same problem to solve...

Katalin Wagner
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 7, 2022

We have similar problem: we'd like to list all the issues that were brought to a sprint (called as inherited) in an "in progress" state either because they had not been finished in the previous sprint or because their implementation was suspended and now it is about to continue. These issues are not added after the sprint starts but before that, but the stories are already started. In other words we are looking for those issues whose  new-to-in progress transition was before the given sprint started.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events