Working in BPO means strict turnaround times. I’m looking for advice on setting up Jira Service Management (JSM) automation that goes beyond simple notifications. How are you handling 'near-breach' alerts for management without creating notification fatigue for agents? Are there specific dashboard gadgets you recommend for real-time monitoring?
I have my SLA notifications set up to warn the assignee 5 minutes before the SLA breach as an internal comment within the ticket. If the ticket is unassigned and is about to breach, then it'll notify the whole team Slack channel instead. It could be a bit noisy for the assignee, but this method ensures only the person who needs to know is notified. I haven't figured out how to tie in time off schedules, but let me know if you find out.
The new version of dashboards on home.atlassian.com is in early access mode if you want to ask your Jira admin to turn it on for your site/project, but it looks like they only have "Count of work items that breached SLA" which doesn't help that much, but it does provide insights into what can be improved in the future. I hope they add SLA remaining time as a field in the new dashboards soon.
I also have a queue for each team/manager and add the SLAs as the first columns. Then everyone can easily see a counter of how much time is left.
Hi @Shamim Ayub
For high-velocity teams, I’d avoid sending every SLA warning to everyone. It usually creates noise very quickly.
A better pattern is to separate SLA notifications by urgency and audience:
* early warning to the assignee or responsible team* near-breach alert to a lead or manager* escalation only when the SLA is actually exceeded* dashboards/reports for management visibility instead of constant manual updates
This is where a dedicated SLA app can help. My team develops SLA Time and Report for Jira, and it supports before-breach notifications, so you can notify selected users or groups when a certain part of the SLA time is already spent, for example, 80% or 90%.
You can also configure automated actions for exceeded SLAs, such as sending a notification, changing assignee, priority, or status, and notifying via Slack. This helps keep agents focused while still giving leads visibility before work becomes critical.
For monitoring, the SLA Grid Report and SLA Chart Reports can help managers see which tickets are on track, at risk, or already exceeded. SLA charts can also be added to Jira Dashboards as gadgets, so teams do not need to open each ticket to understand SLA performance.
So my recommendation would be: keep notifications targeted, use near-breach alerts only for the right audience, and use dashboards/reports for ongoing visibility.
If you need help setting it up or to understand whether this app will really help you, I suggest you book a 1:1 to discuss all the details.
Regards!
Hi @Shamim Ayub - Just an FYI - We have our local ACE meeting here tomorrow, Wednesday evening at the local Atlassian office in midtown NYC. Please see details to register here: https://ace.atlassian.com/events/details/atlassian-new-york-presents-team-26-recap-and-practical-ai-for-devops-and-it-teams/
We have time for networking and chat and I am sure other folks will be happy to discuss your question!
It looks like you're new here. Sign in or register to get started.
