-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
196
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Problem Definition
JQL does not have a means for users to be able to search for which issues have been added or removed from a sprint.
Suggested Solution
Create a new JQL function that can do this natively
Why this is important
It would help identify these issues in searches, but also then could be very useful on board say as a quick filter to see very fast which issues were added after the start of a sprint.
Workaround
This is something that 3rd party plugins have already achieved, such as Scriptrunner in https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_addedaftersprintstart
Original description:
It could be useful to be able to search for issues that were added or removed from a sprint during it's progress.
A customer even tried to get help from Script Runner support, but the according to the support, the respective function that could return that result is available only to the Server version of Script Runner.
It would be great to have it built natively.
- is cloned from
-
- Gathering Interest
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-20097] JQL search for issues added and removed from a sprint
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.
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.
We need this without using third party or plugin.