SLAs breaching added to board insights panel

[#1]

Hello community! 👋

Sharing news about an exciting a new addition to the issues for attention insight! SLAs breaching will now be included in the board insights panel alongside your stuck and blocked issues 🥳.

The issues for attention insight for Jira Service Management boards surfaces your 30 highest priority issues, making it easier to find and address important work.

You can now see issues that have breached, or are within 30 minutes of breaching their Service Level Agreements (SLAs) alongside your stuck and blocked issues to help you and your team can decide what to pay attention to next.

Select Views in your project navigation, then select the Board tab, then select the Insights button to see your issues for attention. If you don't have Views in your navigation, or don't have boards enabled on your project, an admin can enable them from the Features page in your Project settings.

Using the insights panel

There are three types of issues that appear in the insights panel: issues breaching SLAs, stuck issues, and issues that are blocked by their dependencies. You can see a summary of all these issues in the 'All' tab, or dive into a specific set of issues as needed.

All is the default tab and shows all of your issues for attention. This list may include issues that are stuck, blocked or breaching an SLA. Issues in this list may also be a combination of all three.

SLA breaching issues have breached or are within 30 minutes of breaching their Service Level Agreements (SLAs). Read more about SLAs.

Blocked issues are linked to their dependencies using the Blocked by link. 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. Find out more about linking issues.

Stuck issues are automatically labeled as stuck when they’ve been in the same status for too long. If the issue has stayed in the status longer then 85% of other issues, it will be considered stuck.

So how is overall priority determined?

Since the insights panel shows only the 30 highest priority issues on your board, these issues are automatically ordered to make it easier for you and your team to decide what to pay attention to next.

Five main factors are used to order these 30 issues: the priority field, SLA status, due date, stuck duration, and blocker size. Find out how the the issues for attention insight prioritises your work.

What’s next?

We would love to hear your feedback and based on it we’ll be exploring more improvements in the coming months, as well as looking at more possible tabs and features for the insights panel.

Share this news with your teammates and leave us comments below about what you're finding useful and any suggestions on what could be improved.

Best,

The Atlassian Team 💙

[Tim Eddelbüttel]

SLA breaching issues have breached or are within 30 minutes of breaching their Service Level Agreements (SLAs).

Sometime, i have situations with customers where the SLA goal (e.g. first response on a P1 incident) is less than 30 minutes. Is there any logic in such cases,
e.g. if goal < 3m then near breach will be goal / 2?

Stuck issues are automatically labeled as stuck when they’ve been in the same status for too long. If the issue has stayed in the status longer then 85% of other issues, it will be considered stuck.

Is the label removed when the status is changed? Any way to configure this? For example the workflow has an existing follow-up status with due-date enforcements? What is considered as too long?