Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your existing Jira Software Cloud site 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.
Create powerful rules to start automating your manual, repetitive processes.
The following information only applies to team-managed, scrum projects. This is a beta feature.
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 or issues.
The sprint commitment insight looks at the average story points, or issues, completed 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, either story points or time.
As you plan, the story points 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.
To see what was committed to in previous sprints, hover your cursor over the grey bars.
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?