Creating a sprint in Jira takes about thirty seconds. What separates teams that ship from teams that scramble is everything around that click: what goes into the sprint, when it starts, and how cleanly it closes. This guide walks through the mechanics — creating, starting, and completing a sprint in Jira Cloud — and the handful of gotchas (permissions, board types, parallel sprints) that stop the buttons from appearing at all.

Before you create a sprint: two prerequisites

First, sprints only exist on Scrum boards. If your project uses a Kanban board, there is no sprint to create — the backlog flows continuously. If you need sprints, create a Scrum board for the project (Board menu → Create board → Scrum) or check which board type you are on before hunting for a missing button.

Second, a sprint is only as good as the backlog behind it. Issues should be estimated, prioritized, and small enough to finish within the sprint before they ever enter one — that is the job of backlog refinement in Jira. A refined backlog turns sprint creation from a negotiation into a selection.

How to create a sprint in Jira

1. Open your Scrum project and go to the Backlog view in the left sidebar.
2. Scroll to the top of the backlog. If no future sprint exists yet, click Create sprint. Jira adds an empty sprint container above the backlog.
3. Rename it (⋯ menu → Edit sprint). Skip “Sprint 47” — a name that carries the sprint goal (“Checkout — payment retries”) makes every report and standup easier to read.
4. Drag issues from the backlog into the sprint container, or use right-click → Send to → sprint.

At this point the sprint exists but has not started — it is a plan, not a commitment. You can create several future sprints this way and stage work into them.

How to start a sprint in Jira

With at least one issue in the sprint, click Start sprint. Jira asks for three things: the duration (1–4 weeks; two weeks is the most common default), the start date and time, and the end date, which Jira fills in from the duration. Add the sprint goal here if you did not set it earlier — boards and reports display it, and it is the single sentence that keeps mid-sprint scope arguments short.

Two things to know before you click Start. A board normally allows one active sprint at a time — starting a second requires the parallel sprints feature (enabled site-wide by a Jira admin). And starting a sprint requires the Manage sprints project permission — one of the most common reasons the button is greyed out.

Why can’t I create or start a sprint?

• No Create sprint button: you are on a Kanban board, or the backlog feature is disabled for the board.
• Button visible but disabled: you are missing the Manage sprints permission — ask a project admin to grant it (it is separate from Edit issues).
• Cannot start a second sprint: parallel sprints is off. Decide whether you truly need concurrent sprints on one board — most teams are better served by one sprint per board.
• Start sprint greyed out: the sprint is empty. Jira will not start a sprint with no issues.

How to complete (close) a sprint

When the end date arrives, click Complete sprint on the board. Jira asks what to do with unfinished work: move it to the next sprint, back to the backlog, or into a new sprint. Do not let incomplete issues roll forward on autopilot — each one is information. A story that rolls over twice is usually too big, blocked, or was never ready; route it through refinement rather than straight into the next sprint.

Closing on time matters more than it looks. A sprint that quietly runs long corrupts velocity data, which corrupts every forecast built on it — capacity plans, release projections, all of it.

Creating the sprint is easy — filling it well is the work

Everything above is mechanics. The decisions that make a sprint succeed — setting a goal worth committing to, planning against the capacity your team actually has after PTO and meetings, and not over-filling the container you just created — happen in the planning session itself. For that, see our practical guide to sprint planning in Jira: a six-step walkthrough from sprint goal to commitment.

Automate the start and close

If your team runs a fixed cadence, there is no reason a human should be clicking Start sprint at 9:00 on alternate Mondays — or forgetting to. Sprint Automation for Jira starts and closes sprints on schedule, rolls unfinished work over by your chosen rule, and keeps an audit trail of every lifecycle event — so the cadence holds even when the Scrum Master is on leave.

Rob Borges

Rob Borges spent the first half of his career hunting waste as a Lean Six Sigma Master Black Belt and wrangling portfolios as a PMI Portfolio Manager — until he realized the tidiest process on earth still can't out-plan an optimistic human. So he switched sides and became an Agile Coach. These days he helps Kanban, Scrum, and Agile-at-Scale teams trade gut-feel deadlines for flow data, turning "we'll probably ship sometime in Q3" into release dates leaders can actually take to the board. His rule of thumb: hope is not a forecast, but your throughput history usually is.

See Full Bio