Risks play a critical role in highlighting sprints or issues that may not be progressing as anticipated. It draws attention to potential problems or delays in the project timeline. These risks can be individually tracked, which enables project managers to either activate or deactivate them based on the project’s evolving status. Furthermore, each risk can be assigned a severity level. This allows for a more distinct understanding of the impact each risk may have on the overall project.
When an issue or sprint reaches a predefined risk threshold, a visual alert is automatically triggered on the project timeline. This indicator marks the presence of a risk and its severity. Thus, team managers can assess, classify and prioritize the urgency of the potential impact and the severity of the risk.
Overall, the Risk View Settings helps prioritize which risks require immediate attention and resources to mitigate, ensuring the project stays on track.
Sprint Risk Settings
Get notified about potential sprint risks, including approaching deadlines with unresolved issues, progress that are behind the schedule, scope changes, overdue sprints, and pending sprints past their start date. Help and improve your team to stay on track and address potential challenges.
To set the severity level for each setting, use the provided dropdown control.
Sprint end date is less than # days away and more than #% of issues are not Done
Get visual notifications if the end date of the sprint is less than the defined number of days; and how much percentage (max 100%) of the issues that are still in an incomplete state.
Sprint progress is # percentage points lower than expected
See visual cues if the sprint progress1 is lower than the defined number of percentage points.
1 The expected progress calculation is based on completed issues, total number of issues and the sprint duration. For example, for a two-week sprint (14 days) with 14 issues — the expected progress would be 1 issue in the Done status per day.
Sprint scope has been changed
Get visual alerts if the sprint scope has changed2 at any point from when it started.
2 Indicates an issue was added or removed from the sprint at any point after it was started.
Sprint is completed, but contains issues that are in progress
See visual warnings for completed sprints which contains issues that are still in progress.
Sprint is active beyond its end date
Get visual notifications if a sprint is still active past its due date.
Sprint has not been started and its start date is in the past
See visual alerts if a sprint has not been started for a long time.
Issues Risk Settings
Get notified when issues remain inactive for a set period, lack an assignee, or exceed expected work hours, helping maintain workflow efficiency and accountability.
To set the severity level for each setting, use the provided dropdown control.
Issue is stagnant (no activity) for # days from last activity
See visual notifications when an issue is inactive for the defined number of days.
Issue is stagnant (no activity) for # days from the last status change
Get visual cues when an issue is inactive for the defined number of days from the last time its status was changed.
No assignee for # days
See visual alerts if an issue has no assigned user for a defined number of days.
More than # hours work of time logged
Get visual notifications if an issue has exceeded the defined number of time logged for work in hours.
Pull Request Risk Settings
No activity on PR # days since last activity
See visual representation alerts for pull requests that have been inactive for a defined number of days since the last activity.
More on Team Insights for Jira Cloud
Risk View Settings (this page)
