Running sprints in a Scrum project

sprint — also known as an iteration — is a short period in which the development team implements and delivers a discrete and potentially shippable application increment, e.g. a working milestone version. If you haven't run sprints before, we recommend using a fixed two-week duration for each sprint. It's long enough to get something accomplished, but not so long that the team isn't getting regular feedback.

Note, sprints do not apply to Kanban projects.

In Jira Software, you view sprints on a board and assign issues to sprints. You can search for issues in upcoming sprints using the Sprint field. You can view the Sprint field on each individual issue as well, to see the sprint that an issue is part of. 

To learn more about running sprints, read the following topics:

Known issues

This table lists known issues in the behavior of and in your work with sprints. Here, you'll also find possible solutions and temporary workarounds.

We are aware of these issues and have planned their resolution in future releases.



Closed and completed sprints get automatically removed from the Sprint issue field when you’re moving issues to a new project.

This is a known issue tracked in the ticket JSWSERVER-13333 - Getting issue details... STATUS

See the Knowledge Base article to know more about the issue

Last modified on Jan 3, 2023

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.