• 4
    • 6
    • 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.

      A customer would like to be able to get the percentage of issues rather than the number that pass or fail an SLA.

      For Example:

      • Create an SLA.
      • In reports, have a report to get issues that breached SLA.
        • This will show the number

      Wanted Feature

      • Add in a feature to show the percentage that meet the query as customer requires this.

      How this can be implemented

      • JIRA can currently count the number of issues that meet a query as well as total number of issues within a particular (e.g. It can get the total number of issues in that SLA as well as the number that breached or passed the SLA).
      • Allow JIRA to then compute using mathematical percentage equation the number that is expected and put this value in a field.

            [JSDSERVER-1980] Show Percentage of Issues that Breach SLA in Report

            Percentage of issues that Breached in report is absolutely must. It is only value in percents that is worth to track, because met % report shows 0% if there is no breached and no met issues in a given period. So even if you are perfect in a long run, graph of met % will show spike down in described situation.

            As an user, I consider this as key missing functionality in SLA reports module

            Paulius Zdanavičius added a comment - Percentage of issues that Breached in report is absolutely must. It is only value in percents that is worth to track, because met % report shows 0% if there is no breached and no met issues in a given period. So even if you are perfect in a long run, graph of met % will show spike down in described situation. As an user, I consider this as key missing functionality in SLA reports module

              Unassigned Unassigned
              ijimoh Ismael Olusula Jimoh (Inactive)
              Votes:
              20 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated: