Is there a way to list all active sprint names on all projects in the jira instance

[Sandra Fuchs]

I want a list of all active sprints in jira from all projects.  As admin there are times when a scrum master does not start the sprint on time and I need a way to identify those team's that are delayed.  

If I were writing the query in a SQL language, pseudocode would be something like this:

      Select sprint name from all Jira projects where active sprint is true

I know this doesn't exist in Jira, but there has to be a way to produce a list of all active sprint names in Jira.

Any help would be appreciated.

[Trudy Claspill · Accepted solution]

What exactly do you mean by "active" sprints? If you choose "Active Sprints" from the navigation pane of a Scrum board, what you get is the board view that shows sprints that have been Started. Are those the sprints you want? Not the ones that have already ended, or the ones that have not yet been started?

How do you know the scrum master hasn't/didn't start a given sprint on time?

Do you need other information about the sprints?

All the search capabilities in Jira are oriented around finding issues. You could use a JQL such as

sprint in openSprints()

to get a list of all issues in Active (started) sprints. You could feed that information into the Two Dimensional Statistics gadget to get a list of issues per sprint, which would give you the list of sprints.

However, that works on the assumption that every started sprint has at least one issue in it that is visible to you. If Issue Security is enabled then some issues may be hidden from you. Or if you don't have Browse Projects permission for some projects then sprints associated with the issues in those projects would be hidden from you.

openSprints() gives you issues in started sprints. Addition functions are closedSprints() and futureSprints().

[Steven Hill]

This is complicated by stories that are not completed and move on to a subsequent sprint. The gadget will show all sprints listed in the issue including closed sprints. This pollutes the gadget with closed sprints.

Any ideas?