Creating & Editing Sprints

Plan a Sprint

Every sprint starts with a planning meeting. When planning a sprint, your team would typically commit to deliver a set of stories that are pulled from the top of the backlog. In Jira Software, you view sprints on a board and assign issues to sprints. You can view issues in upcoming sprints on the Team -> Sprints page. This involves creating a sprint, assigning stories to the sprint, and starting the sprint. The instructions on this page will help you complete these activities.

Before you begin

  • Sprints only apply to Scrum Teams.

Creating a sprint

You can create a sprint for your current iteration, or multiple future sprints if you want to plan several iterations ahead.

  1. Go to the Sprints of your Scrum Team.

  2. Click + Sprint button.

Editing the Sprint Information

When you toggle "Sprint Details", you are able to set the Sprint Title, Start / End Dates, Sprint Capacity, and even set the individual Capacity for each Team Member. This will allow you to see how close you are to your teams overall capacity, and how much capacity an individual team member has for the Sprint.

Adding issues to a sprint

In Scrum, scope creep during a sprint should be avoided. In addition, the team is supposed to deliver a working piece of software at the end of the sprint. This means that you need to know your team's capacity for work, as well as the amount of work they are committing to, when adding issues to a sprint.

Typically, your team would estimate issues before adding them to the sprint, so that you can see the total estimated work for the sprint (in the sprint footer). You can match this against your team's capacity for work by looking at past sprints. Tools like the Velocity Chart and Burndown Chart can help you with this. Don't worry if you don't have any historical data — you'll get a good idea of your team's velocity once they start completing sprints.


  • Children can be moved independently of their parents.
  • An issue can only be assigned to one active sprint or future sprint. This means you can't add an issue to both an active sprint and a future sprint at the same time.
  • You can add any issue to any active or future sprint, as long as it is assigned to that team. 
  • A sprint appears ONLY on one teams board. Each team operates independently.

There are three ways to add an issue to a sprint:

Edit the Sprint, and drag items to the "Sprint Backlog"

In the Sprints Section, drag and drop the issues onto the relevant sprint (planned or active)

Start a sprint

Once you have finished creating and editing your Sprint, and when you are on the day of your Sprint Start Date, navigate to your Team -> Sprints Page, and click the Green "Start Sprint" button. This will kick off your sprint. All work items you have in your "Sprint Backlog" will be moved to the first phase of your sprint, and in the same order your have in your Sprint Backlog.

Stop a sprint

At the end of your Sprint, or if you need to end it for any reason, you can click the Red "End Sprint" button either on the "Team Board" page or the "Sprint Planning Page". Once you click "End Sprint", a confirmation will appear asking you to confirm you wish to end your sprint. All ended sprints will have their burndown chart available to them to show you how you did on projected capacity versus velocity.


  • Any Work Items that are in an "Active" or "Halted" phase of the Sprint when it is ended, will be automatically moved to the Team Backlog.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.