You've got a backlog full of stories. Your team is ready to work. But when you try to create a sprint in Jira, the button is greyed out or your board just won't cooperate.
Your standup starts in twenty minutes. Stakeholders want a progress update. You're stuck clicking through menus trying to figure out why you can't start a sprint while your team waits.
The good news? Creating a sprint in Jira is simple once you know the exact steps. I'll walk you through the entire process — from board setup to sprint launch — so you can get your team moving fast.
How to Create a Sprint in Jira: Step-by-Step
To create a sprint in Jira, open your Scrum board's backlog view, click the "Create Sprint" button, name your sprint, set a goal, add issues from your backlog, then click "Start Sprint" to activate it.
Let me break down each step so you can follow along without getting lost.
Step 1: Open Your Scrum Board Backlog
Navigate to your Jira project and select your Scrum board from the left sidebar. Click "Backlog" to see all your unassigned issues. You'll see your backlog listed vertically with epics, stories, and bugs.
If you don't see a Backlog option, your board might be set to Kanban mode. Sprints only work on Scrum boards. You can check this by going to Board Settings → General → Board type.
Step 2: Click the "Create Sprint" Button
At the top of your backlog view, you'll see a blue "Create Sprint" button. Click it. Jira instantly creates a new sprint section above your backlog with a default name like "Sprint 1" or the next sequential number.
But here's the truth: the button is sometimes greyed out. This usually happens when you lack the "Manage Sprints" permission or when another active sprint already exists on the same board. Check with your Jira admin if the button stays disabled.
Step 3: Name Your Sprint
Click on the default sprint name to edit it. Use a naming convention that makes sense for your team. Common patterns include "Sprint 42," "Sprint Q1-W3," or a theme name like "Sprint: Checkout Redesign."
Consistent naming helps everyone track sprints across reports and retrospectives. Pick a format and stick with it across all future sprints.
Step 4: Set a Sprint Goal
Click "Add sprint goal" below the sprint name. Write a one-sentence description of what the team aims to deliver. For example: "Complete the checkout flow redesign and fix top three payment bugs."
A clear sprint goal gives your team a north star. When priorities shift mid-sprint, the goal helps you decide what stays and what gets pushed.
Step 5: Add Issues to Your Sprint
Drag stories from your backlog up into the sprint section. You can also right-click any issue and select "Move to Sprint." As you add issues, Jira shows the total story points at the top of the sprint.
Here's why this matters: if your team's average velocity is 30 points, you'll see immediately when you've overcommitted. The point counter turns red when you exceed your typical capacity.
Step 6: Click "Start Sprint"
Once your sprint is loaded with issues, click the "Start Sprint" button in the top-right of the sprint section. A modal pops up asking for sprint duration, start date, and end date.
Set your sprint length — most teams use one or two weeks. Jira auto-fills the dates, but you can adjust them. Click "Start" and your sprint goes live.
The best part? Your board instantly switches to the Active Sprints view. Issues move to "To Do" columns, and your team can start dragging them across the board.
Prerequisites: What You Need Before Creating a Sprint
Before you can create a sprint, a few things need to be in place. Skipping these prerequisites is the number one reason teams get stuck.
Your board must be a Scrum board. Kanban boards don't support sprints. If your project uses Kanban, you'll need to create a new Scrum board or convert the existing one through Board Settings.
You also need the "Manage Sprints" permission. Without it, the Create Sprint button stays greyed out. Your Jira admin can grant this through Project Settings → Permissions → Manage Sprints.
Your backlog should be groomed. Trying to create a sprint with a messy backlog is like packing for a trip with clothes scattered across the floor. Spend time estimating and prioritizing stories before sprint creation day arrives.
Sprint Planning Best Practices in Jira
Creating a sprint is easy. Planning one well takes discipline. Here are practices that separate smooth sprints from chaotic ones.
Check Your Velocity Before Loading the Sprint
Look at your last three completed sprints. Average the story points your team delivered. Use that number as a capacity guide. If your velocity is 28 points, loading 45 points into the next sprint sets you up for failure.
Jira displays velocity in the Velocity Chart report. Find it under Reports → Velocity Chart. The bar chart shows committed versus completed points per sprint.
Write a Sprint Goal That Actually Guides Decisions
A sprint goal like "complete 8 tickets" tells you nothing. A goal like "ship the user registration flow end-to-end" gives your team clarity. When a critical bug pops up mid-sprint, the goal helps you decide whether to pivot or stay the course.
Leave Buffer for Unplanned Work
Most teams plan at 80% capacity. If your velocity is 30 points, plan for 24 points of committed work. The remaining capacity absorbs bugs, urgent requests, and unexpected complications.
You might be wondering: what happens to leftover capacity if nothing urgent comes up? Your team pulls the next priority story from the backlog. Win either way.
Managing Your Sprint After Creation
Once your sprint is live, the real work begins. Here's how to keep things on track.
Run Effective Daily Standups
Use the Active Sprints board during standup. Have each team member walk through their in-progress tickets. The board gives visual context — everyone sees what's moving and what's stuck.
If a ticket hasn't moved in three days, that's a red flag. Address blockers immediately rather than waiting for the sprint review.
Monitor Your Burndown Chart
The Burndown Chart shows how much work remains versus the ideal progress line. Access it through Reports → Burndown Chart. A healthy sprint trends downward steadily. A flat line means work is stuck.
Check the chart every couple of days. If your line goes flat or rises, something needs attention — a blocker, an underestimated story, or scope creep.
Close the Sprint Properly
When the sprint ends, click "Complete Sprint" in the Active Sprints view. Jira asks what to do with incomplete issues. Move them to the next sprint or back to the backlog.
Closing the sprint generates a Sprint Report automatically. Review it with your team during retrospective. Discuss what went well, what didn't, and what to change next time.
Common Sprint Setup Mistakes to Avoid
Even experienced teams stumble on sprint setup. Here are the mistakes I see most often.
Creating Sprints on the Wrong Board Type
A team sets up their project using a Kanban board, then wonders why sprint features are missing. Scrum and Kanban serve different workflows. If you need sprints, start with a Scrum board template.
Fix: Create a new Scrum board using the same project. Go to Boards → Create Board → Scrum. Select your existing project and save.
Overcommitting on Story Points
Teams new to agile often load 50 points into a sprint when their velocity is 25. The sprint crashes by day five. Half the stories roll over, and morale drops.
Fix: Track velocity for at least three sprints before trusting your estimates. Start conservative. It's better to finish early and pull more work than to miss every deadline.
Skipping the Sprint Goal
Without a sprint goal, your sprint becomes a random collection of tickets. Team members optimize for individual tasks instead of collective outcomes. Stakeholders can't tell whether the sprint succeeded.
Fix: Spend five minutes during planning to agree on one sentence describing the sprint's purpose. Write it in the sprint goal field and reference it during standups.
ONES.com — A Unified Platform for Agile Project Management
If you're exploring alternatives to Jira or looking for a platform that combines project management with broader team collaboration, ONES.com offers a comprehensive suite worth considering.
ONES.com brings together project planning, sprint management, and team collaboration in a single platform. Here are the key capabilities relevant to agile teams:
- Sprint and iteration planning: Create sprints, set goals, and manage backlogs with a visual planning interface designed for Scrum workflows.
- Customizable boards: Switch between Scrum and Kanban views without rebuilding your project structure. Adapt the board to your team's process.
- Burndown and velocity reporting: Track sprint progress with real-time charts that update as your team moves work forward.
- Capacity planning: See team availability and workload distribution before committing to sprint scope. Avoid burnout before it happens.
- Automated workflow transitions: Set rules that move tickets automatically when conditions are met. Reduce manual overhead during busy sprints.
- Cross-project visibility: View sprints and progress across multiple projects in a unified dashboard. Useful for teams managing interdependent deliverables.
- Time tracking: Log effort directly on issues. Compare estimated versus actual time to improve future planning accuracy.
- Custom fields and issue types: Tailor issue structures to match your team's terminology and workflow stages without workarounds.
- Integration ecosystem: Connect with development tools, version control systems, and communication platforms to keep everything synchronized.
- Role-based access control: Manage who can create, edit, and close sprints with granular permissions that match your team structure.
For teams evaluating their project management tooling, ONES.com provides an all-in-one approach that reduces the need for multiple disconnected tools.
Common Challenges When Creating Sprints
The "Create Sprint" Button Is Greyed Out
Problem: You see the button but can't click it. Nothing happens when you try.
Solution: Check two things. First, verify your board type is Scrum, not Kanban. Second, confirm you have "Manage Sprints" permission in Project Settings → Permissions. If not, ask your Jira admin to add your role.
Sprint Disappears After Creation
Problem: You clicked "Create Sprint" but it vanished from the backlog.
Solution: The sprint likely started automatically or got assigned to a different board. Check the Active Sprints tab. Also verify you're viewing the correct board — multiple boards can share one project.
Can't Add Issues to the Sprint
Problem: You drag stories into the sprint, but they bounce back to the backlog.
Solution: The issue's status might not map to a column on your board. Go to Board Settings → Column Mapping and ensure all statuses have a corresponding column. Unmapped statuses prevent issues from appearing on the board.
Story Points Don't Show Up in the Sprint
Problem: You added issues but the point total reads zero.
Solution: Your estimation field might be set to a custom field instead of "Story Points." Check Board Settings → Estimation → Estimation Statistic. Set it to Story Points (or your preferred field).
Two Sprints Started Simultaneously
Problem: You accidentally started a second sprint while one was already active.
Solution: Jira allows parallel sprints only if enabled in Board Settings → General. To fix, complete or stop the incorrect sprint. Going forward, always check the Active Sprints tab before starting a new one.
Frequently Asked Questions
Can I create multiple sprints at the same time in Jira?
Yes. Jira allows you to create multiple future sprints in the backlog. You can have one active sprint while planning the next two or three. However, only one sprint can be active per board unless you enable parallel sprints in Board Settings. Most teams plan one sprint ahead while the current one runs.
What happens to incomplete issues when I close a sprint?
When you click "Complete Sprint," Jira prompts you to handle incomplete issues. You can move them to the next sprint, return them to the backlog, or leave them in their current state. Most teams move carryover stories to the next sprint, but returning them to the backlog forces a re-prioritization conversation.
Do I need a Scrum board to use sprints?
Yes. Sprints are a Scrum-specific feature in Jira. Kanban boards use a continuous flow model without time-boxed iterations. If your project currently uses a Kanban board, create a new Scrum board that references the same project. Your issues will appear on both boards without duplication.
How do I change the sprint duration after creating it?
You can edit sprint duration before starting it by clicking the sprint name in the backlog. After starting, click the sprint name in the Active Sprints view to modify dates. Changing the end date mid-sprint is possible but disruptive. Lock your sprint length during planning and stick with it for consistency.
Why does my sprint show zero story points?
This happens when your board's estimation statistic is misconfigured. Go to Board Settings → Estimation and check the "Estimation Statistic" field. It should be set to "Story Points" or whatever custom field your team uses for estimates. Issues without estimated points also contribute to a zero total.
Conclusion
Creating a sprint in Jira comes down to seven steps: open your Scrum board backlog, click "Create Sprint," name it, set a goal, add issues, configure dates, and click "Start Sprint."
The teams that struggle aren't missing technical skills. They're skipping prerequisites — wrong board type, missing permissions, ungroomed backlogs. Handle those first, and sprint creation becomes a five-minute task.
Remember the frustration of a greyed-out button before your standup? With the right setup and a clear process, that scenario disappears. Your team walks into planning, creates the sprint, loads it with well-estimated stories, and launches with confidence.
Whether you stick with Jira or explore platforms like ONES.com, the fundamentals stay the same. Know your velocity. Write a meaningful sprint goal. Leave room for the unexpected. Close the sprint cleanly and learn from it.
Your next sprint starts with a single click. Now you know exactly where to find it.
Top comments (0)