JQL for issues added to Sprint after sprint start date

[Chris Rees]

We need to use JQL to find issues added to a Sprint after the start of that sprint.

The following posts are all requests for the same function. Surely Atlassian can see there is a want/need for a pretty basic feature and users feel that we shouldn't have to pay for an additional add on to get it.

Does anyone at Atlassian have a comment on this?

https://community.atlassian.com/t5/Questions/Scope-Change/qaq-p/40228

https://community.atlassian.com/t5/Jira-questions/Changes-to-Sprint-after-Sprint-start/qaq-p/856446

https://community.atlassian.com/t5/Jira-Core-questions/how-do-I-identify-issues-added-to-a-sprint-after-it-has-started/qaq-p/299931

https://community.atlassian.com/t5/Adaptavist-questions/Added-after-sprint-start-how-to-visualize-it-better-on-the-board/qaq-p/720626

https://community.atlassian.com/t5/Jira-questions/Create-a-quick-filter-query-to-show-issues-added-to-current/qaq-p/367806

https://community.atlassian.com/t5/Questions/Is-it-possible-to-check-the-date-when-an-issue-has-been-added-to/qaq-p/406992

https://community.atlassian.com/t5/Jira-Core-questions/how-to-find-tasks-added-to-sprint-after-it-started-bugs-added-to/qaq-p/6251

https://community.atlassian.com/t5/Answers-Developer-Questions/Determine-when-an-issue-was-added-to-a-sprint/qaq-p/553892

https://community.atlassian.com/t5/Jira-questions/JQL-to-determine-what-issues-have-been-added-after-sprint-start/qaq-p/778281

https://community.atlassian.com/t5/Jira-questions/What-JQL-query-is-used-to-see-issues-added-to-a-Sprint-after-a/qaq-p/586225

[Andy Heinzer]

Hi Chris,

Thanks for bringing this to our attention.  That certainly does look like a comprehensive list of Community posts with users that also want to be able to search JQL to find issues added or removed from a sprint after start. 

You can find these issues in the burndown chart on a per sprint basis. These are reflected a scope change event. I know this is not exactly the same as being able to search for this in JQL that you are seeking here, but for some users might search this topic and find this post it might be helpful for them to know that this report exists.

In regards to your specific request here:

I found there already existed a feature request for this functionality in Jira Cloud in: JSWCLOUD-16523

However surprisingly, there was not an existing request for this in Jira Server, so I created one in JSWSERVER-20097

I would recommend watching that ticket and voting on this as well.  This can help our development team to prioritize new features.  You can see what topics the Jira Server team is looking into by checking out the new dashboard on https://jira.atlassian.com/secure/Dashboard.jspa this shows both bugs and new features that are in progress, being considered, or on a short term roadmap.  

It is probably also a good time to talk about Atlassians Implementation of new feature policy:  It also explains the use of jira.atlassian.com as a means to track these requests and other methods to which you can suggest new features.  Any user can create suggestion tickets for Jira projects on jira.atlassian.com

I agree that there are clearly other users out there that have been seeking a means to do this specific JQL search in Jira.  However JQL is limited in the results and the data it can return being bound to the issues themselves.  This can include the sprint name or sprint id, but it doesn't have the native ability to be able to lookup the sprint start date for starters, secondly JQL cannot lookup historical value changes for most fields of issues (there are a few system fields like resolution, status, etc that have gained a historical search in JQL, but sprint is not one of these).  In my humble non-developer opinion, that would appear to be necessary to do for each issue in order to be able to accurately reflect this information in JQL search results. 

It's not to say it would be impossible to implement in Jira's JQL, just that it's not necessarily an easy win here.  And honestly there are several other features that at least now, appear to have considerable more interest in adding to Jira Server.  

That said, perhaps this request will be considered more closely in the future.  Now that we have a suggestion ticket created for that, it is at least possible now.

Regards,

Andy

[Chris Rees]

Hey Andy,

That's awesome! Thanks for your help and speedy response.

[Marcin Seredyński]

Atlassian, what is the number of votes and time passed that you need to make a decision about approving or rejecting a request?

[M_ S_ Malik]

Update: This is after using paid add-on. Please ignore

Try this JQL:

issueFunction in addedAfterSprintStart("<SCRUM-BoardName>","<SprintName>")

[Reesy]

This is not out-of-the-box JQL. It is only available if you have the paid ScriptRunner installed.

[Kit Teguh]

6 years later and still gathering interest? Not that hard surely? And no, I don't really want to use other paid solutions like Script Runner to run these simple requests.

I can look at the issues added in the reports, but if I want to compile them all into a spreadsheet or table JQL is still the best go to unfortunately.

[bilyana.karayaneva]

We need to be able to pull easy a report based on this. Woudl be great if we can have a section in the SPrint report,issues added after sprint start!