Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Search for issues, navigate to your work, use advanced search, and work with your search results.
Plan and view work across multiple teams, projects, and releases using Plans.
The following information only applies to team-managed, scrum projects.
To check your project type, look at the bottom of your project’s left-hand sidebar. If you don’t see an icon stating You’re in a team-managed project, then you’re in a company-managed project. Check out our company-managed project documentation.
Insights on the backlog provide support for you and your team during sprint planning sessions and retrospectives.
Review your previous sprint commitments during your sprint planning sessions to get an idea of past trends. Look for your ideal range, and aim to assign the target amount of story points, issues or time.
The sprint commitment insight looks at the average story points completed, issues completed, or time logged in the last five sprints to recommend a target range for future sprints. The insight respects the estimation statistic that’s enabled for your project; story points, issue count or time.
As you plan, the story points, time or issues you commit to the sprint will be tallied and compared to your target. Recommendations are automatically calculated if your commitment falls outside the target range, making it easy for you to adjust your scope as you plan.
Access your commitment metrics from your previous or current sprints by selecting the bars on the chart. If you select the current sprint you’re planning the insight will expand to show you the number of points or hours you’ve committed. You can also view the recommended range of points or hours to help you plan for the best outcome.
When selecting a previous sprint, the insight will expand to show your completed points or hours, incomplete work and the total percentage of work completed.
Issue type breakdown
Use the issue type breakdown for sprint planning sessions. Assess the balance of work from previous sprints to adjust, or maintain, your focus next time around.
See the issue type breakdown for your sprint. As work is assigned, the visualization and callout adjust, so you can understand the balance of different work types. The insight only displays the issue types allocated to that specific sprint.
The callout lets you know which issue type appears the most in the sprint. This is useful during retrospectives, so you can reflect on recurring, time-consuming issue types.
During planning sessions, assess your top issue type to make sure your team isn’t heavily focused on bugs and tech debts. Too many bugs and a hefty tech debt could be a cue for your team to focus on quality or block out time to resolve debts.
Hover over the bar associated with each issue type to see the exact number of issues allocated to the sprint, and the percentage it contributes overall.
Was this helpful?