Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

JQL to determine what issues have been added after sprint start


If the Jira Cloud Sprint report can render an * for what items have been added after sprint start, how can I write JQL to do the same thing? From all indications of older posts that, it is not possible, However in 2018 it is crazy that we can't pull this same data out of Jira without spending more money on a plugin if the UI can access this data.

6 answers

Vote for JSWSERVER-20097 to have this built into JIRA Server, or JSWCLOUD-16523 for JIRA Cloud, by default.

We use JIRA 7.12 server version.


We could not find this information, without purchasing a JIRA add-on (Adaptavist Scriptrunner)


Once we had licensed it, the following JQL finds this information:


project = <Project Name> AND issueFunction in addedAfterSprintStart("<Sprint Board Name>") 


Add-on documentation available here.

one problem with this solution (i'm trying to work on the same problem in the last week or so) - the function of addedAfterSprintStart is working on on hosted jira, not on cloud jira.

@Eli Moshe

   Same. We tried using scriptrunner but it doesn't have that feature in the cloud either. It really annoys the hell out of me because the data is available in Jira Cloud, based ont he * used in the sprint report indicating what had been added to the sprint, Altassian is just handicapping their cloud product so you'll buy the cloud hosted/on-prem version. Just a dumb, dumb business practice on their part, and making me have to evaluate what other options are out there since they don't want to give the cloud version parity to hosted/on-prem @Atlassian

Agreed this is ridiculous this doesn't come out of hte box, but THANK YOU to whoever posted the JQL and tip on JIRA add-on (Adaptavist Scriptrunner). Miracle of miracles my org actually has that add-on and that JQL syntax worked perfectly!!!  I just wish i could have it come up in a Y/N as an actual field, but at least with the results i can compare them against the rest of the items in the sprint to figure out the planned/unplanned work ratio. 

Like # people like this

Count me in also for this functionality!

@Troy Spetz Thank you for the answer. Could you please specify the query for the past sprints as well.

To find the issues added after the sprint has started, you can consider using our professional indexing service:

After you install the app you can find out what issues were added after the sprint started:

issue in addedToSprintAfterStart("My board", "Sprint 5")

Make sure to check out the documentation.

I hope it helps!

1 vote

You can determine it using Jira Automation.

Create a rule that is triggered when the field Sprint is updated and a condition to check if Sprint is in an OpenSprint(). You can add a flag in Labels and after that, build a JQL query for that Label and you will get the data you desired.

We do this as our team members need to report on issues added to an active sprint and they need to report on what day they were actually added. 

On the Edit of the issue we set the custom date field to {{now}}.  Probably not perfect, but allows the team to run a JQL for that specific sprint and then they just look for issues where the Added to Active Sprint Date is not Empty


Thanks @Julian Governale for sharing this. I was trying to do the same from long time but is not working for me to get the opensprint() correctly and if condition is failing for me.  Would you mind in sharing the snippet if it is working for me? For your reference adding the snap as well, i have tried different ways as well but no luck.ActiveSprint.png

Can anyone help to cross this stage? It would be a great help.

The condition type is wrong.


You must select JQL Condition. 

Hi @uttam kumar bhatta , @Carlos Neto is correct, you want to use JQL


1 vote
Deleted user Feb 11, 2020

To follow a sprint update / changes is important so implement this feature as standard functionality

0 votes
Deleted user Feb 11, 2020

you support many teams and later you want to follow up on changes, then it should be easy to see what has been lifted into the respective teams sprint after it was started

Suggest an answer

Log in or Sign up to answer