Atlassian will never give us this. They are relying to much on the Add ons build by others. And those people will get angry if Atlassian will build these kind of features. So Atlassian is in a tight spot now. They cannot give us features that are already there in third party add-ons, and they will lose more and more of their user base on when not building these features.

This functionality/data actually exists in the Sprint Retrospective Reports. Kinda strange that it's not exposed in JQL

5f36f87b5c76, This is how I got ScriptRunner to pull those tickets that were added to the Sprint after the Sprint started. 

In ScriptRunner, enter the following code. 

sprint in openSprints()
and sprint not in closedSprints()
and issueFunction in addedAfterSprintStart("Your Scrum Board Name")
and issuetype != "sub task"
and "Product Family / Product Team" in ("Team Name")
ORDER BY Key

This will pull issues that were added after the Sprint started

Then create a regular filter that references the ScriptRunner filter.

sprint in openSprints()
and sprint not in closedSprints()
and filter = ScriptRunner Filter Name 
and issuetype != "sub task"
and "Product Family / Product Team" = "Team Name"
ORDER BY Key

You will then be able to use the results in boards, gatgets, etc. 

One thing I found confusing when I went to edit my JQL filter is that the portiion that says 
"filter = ScriptRunner Filter Name "

Turned into something like this:
"issue in (523983,523989,524223,524738,525277,527969)"

Somehow, this is the list of tickets identified in the ScriptRunner filter. I dont know what those numbers signify though. 

Trying so badly for this too

I was able to get this info using ScriptRunner, but my company is no longer paying for this add on. This functionality should be native to Jira. You already have it working in the Sprint Report, why cant I get that same functionality to populate widgets on my Dashboard which I use in my Daily Stand Up. 

I need it as well.

+1 hoping this will one day be implemented

+1, so am I still waiting 

+1

+1

This feature would give us so much extra control over what is happening with our sprints. This feature is extremely wanted in our team!

+1 

This issue is adressed 5 years ago!!! When does Atlassian think it's created??

+1

+1

+1

The lack of this feature is truly distressing. As others have observed, there is an existing flag that is available on the "Sprint Report" denoted by an asterisk. A report that you cannot even export to csv. The Burndown Chart report produces a list of initial items in a table and provides event details meaning there are in system flags that can be leveraged. Also cannot export. The Velocity Chart captures the Commitment point in some way. I can only assume like others have that this is less of a performance decision and more of a marketing one, locking this crucial information behind paid tools. Introducing the manual waste of directly copying page details into another format for evaluation, a wasteful operation that is at risk of so much human error. Or introducing the need to somehow manually flag these items which is also additional waste in the form of another burdensome task for teams and a gap that manual data entry introduces.

When I go to the Atlassian page on Jira, the first thing I see is
"The #1 software development tool used by agile teams". The marketing here isn't focused on support teams, nor project management teams - it is targeted at Agility. Regardless of the Agile method or framework teams are using, there is a heavy emphasis on empiricism. Basing your current plans on previous performance is absolutely necessary. Being able to understand trends in your team and highlight them is an absolute must to the basics of this product. Without that, I challenge its alignment with being "the #1 software development tool used by agile teams".  Do not send me to third party tools here, when the majority of your userbase would find themselves in a corporate setting where we cannot leverage these tools directly or a private one where these tools may be cost prohibitive. Not for something that should be as foundational as this to your core target market. This is foundational information which can be used to analyze a teams focus, predictability, trends, impacts. Locking their availability to reports which are not easily digestible to a team is not a solution.  Give us the data our teams produce through the same JQL engine you expect us to use for so much other information. Please seriously consider this and thank you.

Well over 5 years and 1.5K votes (between cloud and server tickets) and still waiting ...

+1, especially since this scriptrunner function no longer works on cloud

How many requests are needed before you change the status from gathering interest to assigning it to a developer?? 

We have been waiting for at least a year for the ability to pull this info directly from Jira with a simple JQL statement. 

+1

@atlassian, what do we need to do to get this moving forward. As a development manager, it is incredibly helpful to see what items are being injected, or pulled, from an active sprint. Having the ability to identify these items on a dashboard would be very useful for daily planning and overall visibility. This functionality exists for issues removed from sprint in the standard "Sprint Report", why don't you expose it for JQL. I see that this has been a common request/complaint for years now. A simple JQL feature would be adequate. 

@atlassian, curious how many +1's and years something has to sit in 'Gathering Interest' before someone thinks it has enough interest to implement? Between this issue an the issue it was cloned from, it looks like it could be valuable to a lot of your users

+1

+1

+1 - incredibly sad that the reporting provided to SMs provides only limited data. It seems odd that Jira "knows" this by giving us the not-so-useful asterisks, so it must be in there somewhere. The burndown also provides changes to sprint scope, so why are we not able to hook on whatever Jira is using to pull that information for an actual sprint report, which is where it would be most useful.

+1
This is an essential feature, and it's absence is so frustrating; there are plenty of reasons why we might move a ticket from one sprint to another, and we should be able to query and analyze these transitions. The sprint history is maintained in Jira - the History tab shows every time the Sprint field changes; it's a serious omission that you cannot access this in JQL.

+1

+1

+1. Should be part of the sprint report.

+1 This would make my reporting so much easier! (Company does not want another add-in)

+1

I'm surprised I cannot query this natively using JQL

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

determine what moved
determine which sprint it moved to

+1

Hi everyone, just till this ticket is resolved, you can try GO! JQL: Essential JQL Functions

Doc: https://almbase.atlassian.net/wiki/spaces/MDOC/pages/4100555652/Sprint+JQL+functions

Marketplace: https://marketplace.atlassian.com/apps/1225063/go-jql-essential-jql-functions?hosting=datacenter&tab=overview

@atlassian, Any update on where this stands?  This seems like a common sense feature

+1

Very useful

Please.

+1

+1