> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/settings/team/sprints.md).
# Sprint configuration
To view Jira data in Swarmia, you must first assign the appropriate Jira board to your team.
When you [configure Jira issue ownership mappings](https://github.com/swarmia/knowledge-base/blob/main/getting-started/configuration/broken-reference/README.md), Swarmia will automatically select a board that has Sprints and enable sprint activity tracking.
If your board is not automatically selected or you need to change the board for your team, you can go to [Team issue settings](https://app.swarmia.com/settings/team/issues), click "Track sprint activity" and select the correct Jira board for your team.
{% hint style="success" %}
After configuring the Sprint, you can now go to [Swarmia sprints](https://app.swarmia.com/sprints) and read further at:
* [Sprints](/features/focus/sprints.md)
{% endhint %}
#### Private Jira boards
If your Jira board is private, Swarmia cannot access sprint data from it. Private boards will be indicated with a lock icon (🔒) in the board selector.
To use a private board with Swarmia change the board's permissions in Jira to allow organization-wide access.
### Troubleshooting
If you can't find the board in the selection list, make sure your Jira board filter has organization-wide permissions, allowing the Swarmia app to sync your board.
Please reach out to us at if you experience any issues with the sprint configuration.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.swarmia.com/settings/team/sprints.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
