Disclosure: I'm the developer of SLA Pulse for Jira at PulseRook, an Atlassian Marketplace Partner.
A common SLA problem in Jira is that a Highest-priority Incident and a Highest-priority Service Request rarely share the same target. Until now, SLA Pulse for Jira set rules by priority only. Version 2.7.0 adds issue type as a second dimension.
What's new in 2.7.0
SLA rules per issue type: Set different hours for each priority within each issue type, such as Incident or Service Request.
Your real issue types: The Settings page lists the issue types configured in your project, so you don't need to type them in.
One set of rules everywhere: The dashboard, Slack alerts and the daily digest now read the same rules, so the numbers match across all three.
Existing rules carry over: Rules you've already saved are migrated automatically.
What the app does
- Shows SLA compliance, breached issues and near-breach issues on one dashboard
- Tracks MTTA, MTTR and reopen rate
- Sends Slack alerts and a scheduled daily digest
- Is built on Atlassian Forge and runs inside Jira Cloud
I'd like to hear how your team handles SLA targets across different issue types. What would make that setup easier in your Jira?
SLA Pulse for Jira on the Atlassian Marketplace:
https://marketplace.atlassian.com/apps/3460167006/sla-pulse-for-jira
