Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-1728

SLA Report that would include what team/agent the ticket was when the ticket breached its SLA

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Reports
    • 2
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? 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

      Example Use Case

      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.

              Unassigned Unassigned
              jalor Janice Alor (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: