Add issues to an active sprint
This page is for company-managed projects
To check whether your project is team-managed or company-managed, select more actions (•••) next to the project name in either the header or the sidebar. At the bottom of the menu that opens, you’ll be able to view whether your project is team-managed or company-managed.
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.
To add issues to an active sprint, you must have:
Schedule issue and Edit issue permissions
Add an issue to an active sprint
If not already there, navigate to your company-managed software project.
Add work items from the backlog to an active sprint
From your project’s sidebar, select Backlog.
Drag and drop the work items onto the relevant sprint.
Tip
To add multiple work items:
select the work items (use Shift+Click or Ctrl+Click), right-click, then select the relevant sprint
drag the sprint footer down to include work items from the backlog.
Create a work item and add it to an active sprint
From your project’s sidebar, select Active sprints.
From the navigation bar, select Create.
Fill in the work item details and add the relevant sprint in the Sprint field.
Select Create.
Tip
To create multiple work items, select the Create another work item checkbox.
Was this helpful?