I want to set a filter that filters for issues which are in a particular sprint in Jira. For that purpose I need the sprint ID of a particular sprint. How can I find out the sprint ID of a particular sprint?
Thanks for your help!!
The hack i found was to view the sprint report for an active/closed sprint.
The global Sprint ID will showup in the URL. I would really love AtLSSIAN to add a simple link that jumps to issue navigator, pre-filtered like the old boards did.
Is there a sprint id associated with a future inactive sprint as well? For example, during sprint planning I create a new sprint on the Plan tab for different boards. Then I am writing a jql to pull out issues from "Next" sprints in every board but seems like jira/greenhopper only creates a sprint ID for active sprints?
@nIKHIL, you should start a new question for this topic. But in short no, the future sprints in the planning view are actually called "markers", and I do not think they are available via JQL- https://answers.atlassian.com/questions/52688/how-to-use-rapid-board-s-sprint-marker-in-jql-query, but you can get the list of issues in a future sprint from the rest api.
Also note that there should be a link in planning view on markers that says something like "view in inssue navigator"
This works, but you have to wait a moment for the "autosuggestions" to appear below the JQL entry box and then move the mouse cursor, click on the autosuggestion, and voila, your autosuggestion that was identical to your sprint name is mysteriously replaced in the JQL entry area with the sprint ID. (This is very non-intuitive) I also looked for a column titled Sprint ID that I could simple add to the Issue Query output. Alas, this doesn't exist in the column possibilities.
Note: This wouldn't be such a big problem if it weren't for the compounding restriction in Bulk Update that only Sprint ID's can be used in the Sprint field.
The fact one has to open up the developer tools to look up the sprint id in the code in order to obtain the Jira Sprint ID for the bulk transition to another sprint is asinine. Perhaps Atlassian can make it easier to locate the sprint ID in the transition jiras tool so one does not waste time trying to identify the ID in the first place.
But I digress, thanks for the reminder on this @Corey Scott
@Jason, there's no need to use developer tools, you can see the sprint ID by hovering over as John Smith says. I agree it could be more easily found. Also, it should be used more, e.g. it would be great to have a url including it which allowed the backlog to open with that particular sprint expanded and ll the others collapsed.
What if someone sends you a filter to run with sprint ids only
sprint in (22, 33, 44)
It returns the issues list and looking at the sprint column of the report, you can see them, but if the issue runs across multiple sprints you get multiple user friendly sprint names for a single issue, so how do you know which one correlates to 22, 33, and 44?
Basically looking for a reverse lookup from index to friendly name
There's probably a better solution than this out there, but one way that works, if the sprints were added after ticket creation, is to check the History tab on the ticket. Look for where the sprints were added and it will list out the sprint names, plus their IDs (in same order as name).
Step 1 - Go to the Backlog page
Step 2 - Open Inspect element by right clicking anywhere in the page and selecting inspect (for google chrome)
Step 3 - Search for data-sprint-id in the inspect element section. Beside the entry you would find the id of the sprint in focus in UI.
JIRA maintains an equivalent numeric value for each Sprint. The numeric value is what you need to have in the CSV file,
To find the numeric equivalent of a sprint, do the following : Go to Issue navigator, and specify the following query: sprint = Sprint 18.
When you finish typing Sprint 18, you will see the corresponding numeric value displayed in the query
Last week Megan Cook, Head of Jira Software and Mahreen Khan, PhD, Organizational Psychology hosted an “ask me anything” session focused on the psychology of agile teams. We received 22 questions, 16...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events