how can a Scrum Master figure out how many sprints on his/her current board originated from a different board, without using the API.
need JQL.
Hola,
I don’t think JQL can answer this directly.
JQL searches for issues, not board or sprint metadata, so it can tell you which issues are in a sprint, but it won’t reliably tell you which board a sprint was originally created from or count “sprints on this board that originated from another board.”
A sprint can appear on a board because the board filter includes issues from that sprint, but that does not mean the sprint was created on that board. That board-origin information is board/sprint metadata, not something exposed through standard JQL.
Without using the API, the practical options are pretty limited:
So the direct answer is: this is not possible with JQL alone. You would need the Jira Agile/Software API, or another admin/reporting tool that can access board and sprint metadata.
Thanks,
James
Welcome to the community forums!
There's quite a bit to unpack with your question but I'm confident this simple dashboard solution should provide the information you seek.
In Jira, sprints are tied to work items, not boards.
If your board's underlying filter pulls in an issue that is assigned to a sprint created elsewhere, that entire sprint will show up on your board.
This usually happens if your filter is too broad or if an issue was moved into your project.
JQL doesn't expose a sprint's "origin board," but you can easily map out exactly where these sprints are coming from using a Dashboard gadget.
👉 Create a Dashboard and add a 2D Matrix
Go to a Jira Dashboard and add the Two-Dimensional Filter Statistics gadget.
Set Saved Filter to your board's configured filter.
Set XAxis to Sprint.
Set YAxis to Project.
Click Save.
I hope you find this informative and provides an answer to your question. Remember also, the more context you provide to the community the more precise our answers are able to be. :)
Regards,
Ben
Here's a few screenshots demonstrating multiple company-managed spaces configured with boards that pull work items from multiple boards:
Multiple spaces:
Space Command Board with broad filter scope:
Note: You may also see additional sprints as result of work items being moved from space to space.
Dashboard with gadgets linked to the "Space Command Board's" filter:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Ben Spillane
The Two Dimensional gadget is counting how many issues in the sprint are in the specified project.
It doesn't provide any information about the board in which the sprint was created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's absolutely right, @Trudy Claspill . You can't query or display Jira board objects via JQL.
However, by creating a new filter with one minor tweak, we can get a little bit closer to answering the original question:
"how many sprints on his/her current board originated from a different board"
Create a new filter for the dashboard gadgets to reference:
Dashboard gadgets side by side:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Ben Spillane
However, by creating a new filter with one minor tweak, we can get a little bit closer to answering the original question:
"how many sprints on his/her current board originated from a different board"
Create a new filter for the dashboard gadgets to reference:
This filter will essentially take everything from his/her current board and ensure the filtered work items don't belong to the specified space.
What's left are only items brought in originating from other sprints/boards.
Given that we don't know the actual filter that is being used by the author in the board, what small tweak are you recommending should be made?
@Josephine_Tina_ Albert Can you share with us the filter being used by the board?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian community!
Jira Query Language (JQL) is designed strictly to filter issue data fields and cannot query board configuration metadata or isolate the original source boards of your sprints.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.