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.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
Insights use the latest browser-features. Check which browsers we currently support.
Hit every daily scrum meeting with a dose of insights. As you run through your board, see how your sprint’s tracking to understand the likelihood of completion.
Understand exactly how your sprint's progressing across each status category, making it easier for you and your team to pivot, set expectations, or see work through.
The bar is split by the number of story points, issues, or time assigned to each status category. If your project has story points enabled, the progress bar will update when points are added to each issue.
So, at a glance, you can understand the portion (and percentage) of work that hasn't been started, is in progress, or done.
Hover over each status category section to see a breakdown by story point, issue count or time estimate.
Keep an eye on your priorities and stay on track to achieve your goals by seeing how your sprints contribute to your epics.
Please note that epics can be renamed. The information in this article is relevant, regardless of what epics are called in your instance.
Epics will often represent a big goal, project, or outcome. Instead of tackling everything all at once, Scrum teams often break down big goals into smaller pieces of work that then get added to a time-boxed sprint.
The epic progress insight helps you connect the work you’re doing in your sprint to that larger goal, outcome, or epic. This could mean your sprint only contains issues working towards one epic, such as your launch plan. Or, maybe your team choose to divide and conquer and add work to a sprint that helps to progress multiple epics
The insight also indicates when the issues in your sprint aren’t working towards any epics. This might be because your issues haven’t been assigned to an epic. If the work has been assigned to an epic, and it’s still not showing up in the insight, check your estimation statistic. Right now, insights support story points, time estimation, and issue count.
Keep an eye on your team’s sprint progress as it’s happening. By frequently tracking your output against your goal, you can shift focus, maintain momentum, or take a moment to revel at your pace.
Throughout a sprint, you and your team can track exactly how much work remains compared to how much work was planned. This helps you manage and pace effort, and gives you adequate time to respond to trends.
The Y-axis represents the total amount of work committed to a sprint. As work’s completed, the percentage and corresponding blue line reduce, indicating how much work remains.
The grey horizontal line acts as a guide. It indicates roughly what percentage you’d expect to see at that point in time, in order to reach 0% by the end of your sprint.
In addition to these visualizations, the sprint burndown provides a callout that calculates how many points or issues have been completed, and how many points or issues remain. This is coupled with a status lozenge, reflective of that state. These include:
Your team’s progress is faster than or at the guided rate.
Your team’s progress is slower than the guided rate. This state indicates your workload and rate may need attention.
This makes it easy for you and your team to see how you’re tracking and if necessary, make changes. Hover over the blue shaded area representing the remaining work.
Issues for attention
Stay on top of flagged or blocked issues in your sprint, so you can assess impact, tackle dependencies, and continue to move work forward.
The issues for attention insight surfaces flagged issues and issues that are blocked by other dependent issues, making it easier for you to address high-priority work within your current sprint.
An issue can be flagged via the More () menu found in the top right corner of the issue. Blocked issues are linked to their dependencies using the Blocked by link, found in the quick-add (link-icon) button.
Both flagged and blocked issues will display in the order they appear on your backlog. However, if an issue is flagged and also blocked by another, the insight will present the flagged state first. This is to show that specific issue has been marked as important, and may require more immediate attention.
From the insight, hover and then select to view the flagged or blocked issue. If there are more than five flagged or blocked issues, a link will appear at the bottom of the insight so you can view all issues for attention.
Keep in mind this insight relies on the default state of the blocked by link. If the link has been modified, your issues won’t display in this insight. A flagged issue, that is also using a modified blocked by link will display as flagged.
Was this helpful?