Discussions
-
What’s new in SLA Pulse for Jira 2.9.0: per-project SLA rules, working hours and pause-the-clock
Disclosure: I’m the developer of SLA Pulse for Jira. Until now, SLA Pulse used one set of SLA targets for the whole Jira site. That works for one team, but a support queue and an engineering project rarely want the same numbers. Version 2.9.0 is about fixing that, so each team sees SLA results that match how it actually…
-
What's new in SLA Pulse for Jira 2.7.0: SLA rules per issue type
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…
-
How are you managing SLAs proactively in Jira? (We built a tool to solve this)
Hi JSM admins, We've been active in this community answering SLA questions, and we're seeing a common pattern: most teams track SLAs reactively — they see the breach after it happens. We built SLA Pulse for Jira specifically to solve this. The Problem: Customers see breaches in the portal after the damage is done Teams…
