Set up Jira Cloud
Learn how to set up Jira Cloud and integrate it with other products and applications.
This page applies to company-managed projects only.
Learn more about the difference between company-managed and team-managed projects.
In Scrum, scope creep during a sprint should be avoided. The team is supposed to deliver a working piece of software at the end of the sprint, so when adding issues to a sprint you need to know your team's capacity for work, as well as the amount of work they are committing to.
Typically, your team estimates issues before adding them to the sprint, so 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.
If not already there, navigate to your company-managed software project.
From your project’s sidebar, select Backlog.
Drag and drop the issues onto the relevant sprint.
Tip
To add multiple issues you can:
select the issues (use Shift+Click or Ctrl+Click), right-click, then select the relevant sprint
drag the sprint footer down to include issues from the backlog.
From your project’s sidebar, select Active sprints.
From the navigation bar, select Create.
Fill in the issue details and add the relevant sprint in the Sprint field.
Select Create.
Tip
To create multiple issues, select the Create another issue checkbox.
Was this helpful?