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

SLA Report not working as expected (SLA met vs breached)

    XMLWordPrintable

Details

    Description

      NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      Steps to reproduce:

      1. Apply JIRA Service desk to an existing project that has 30 days+ old issues.
      2. Navigate to the SLA reports in JIRA Service Desk and select SLA met vs breached report.

      Expected Behavior:

      The report should present the breached issues for the past 7 days, 14 days, 30 days, etc accordingly.

      Actual Behavior:

      The report is actually counting older issues as breached with the date the service desk was applied to the project and not with the correct date when it was really breached.

      As you can see on the screenshot below, the project in question had breached issues on October 2014. After applied the the Service Desk to this project it's now counting as breached with the date the Service Desk was applied to the project (Feb 13th).

      Workaround:

      No available workarounds.

      Attachments

        1. Breached.png
          Breached.png
          69 kB
        2. Report.png
          Report.png
          130 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              lfagundes Luciano Fagundes (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync