-
Suggestion
-
Resolution: Won't Fix
-
1
-
NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.
Current Behavior
Currently there is no SLA Report that include what team/agent the ticket was when the ticket breached its SLA
Feature Request
SLA Report that would include what team/agent the ticket was when the ticket breached its SLA
Background: In our organisation we have multiple teams who receive tickets/requests from internal employees or direct from external clients, there isn't a triage structure whereby a ticket always goes to team 1 first, then team 2, etc. Some tickets can also be passed to & from teams if more information is required. So we want our reporting to highlight when a ticket has breached its SLA & the team it was sat in at the time, due to the nature of our Team 3 (invariably the Team 3 to have picked up the ticket) there will be a high volume of tickets that will show the Initial Respond SLA timer (24hrs) as breaching in the Team 3 queue when ideally if the datestamp recorded the team at the same time this would be a more accurate picture of how the Team 1 & Team 2 are performing.
- is detailed by
-
JSDCLOUD-6256 Ability to collect Data on User Assigned During SLA met/breached in Jira Service Management Reports
- Gathering Interest
- is related to
-
JSDCLOUD-1782 Mark Status an Issue Breaches SLA
- Closed
-
JSDSERVER-1728 SLA Report that would include what team/agent the ticket was when the ticket breached its SLA
- Closed