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

Uncaught exception in DateTimeRange during reporting when gathering timeline details

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 4.19.0
    • 4.3.1, 4.13.20
    • SLA
    • None

      Issue Summary

      Some reports in a Service Desk project break when using any time scale above 14 days. This happens during reporting when gathering timeline details.

      Steps to Reproduce

      With JSM 4.3.1, run reports with any time scale above 14 days.

      Expected Results

      Reports should work fine.

      Actual Results

      Reports are failing with the below error.

      2021-01-06 15:53:45,852 http-nio-9000-exec-1893 url:/rest/servicede...desk/IT/report/811 username:motto ERROR motto 953x30902675x2 1w873ps 71.242.86.21,35.190.16.123,130.211.0.71,10.104.5.8 /rest/servicedesk/reports/1/servicedesk/IT/report/811 [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: com.atlassian.servicedesk.internal.sla.metric.DateTimeRange - the START time of the DateTimeRange (2020-11-17T22:24:21.325Z) must be less than or equal to the STOP time (2020-11-17T22:24:13.012Z)
java.lang.IllegalArgumentException: com.atlassian.servicedesk.internal.sla.metric.DateTimeRange - the START time of the DateTimeRange (2020-11-17T22:24:21.325Z) must be less than or equal to the STOP time (2020-11-17T22:24:13.012Z)
        at com.atlassian.servicedesk.internal.sla.metric.DateTimeRange.<init>(DateTimeRange.java:38)
        at com.atlassian.servicedesk.internal.sla.model.Timeline.getRanges(Timeline.java:136)
        at com.atlassian.servicedesk.internal.sla.model.Timeline.getPausedRanges(Timeline.java:81)
        at com.atlassian.servicedesk.internal.sla.metric.TimeMetricCalculationServiceImpl.getAllCycleMetricData(TimeMetricCalculationServiceImpl.java:35)
        at com.atlassian.servicedesk.internal.sla.metric.SLALuceneDocumentDataManagerImpl.getDataFromMostRecentCycle(SLALuceneDocumentDataManagerImpl.java:46)

      The fix for https://jira.atlassian.com/browse/JSDSERVER-6260 was applied specifically to SLA sorting. Here we are seeing issue with reporting.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JSDSERVER-7104] Uncaught exception in DateTimeRange during reporting when gathering timeline details

            Leonardo Souto made changes -
            Affects Version/s New: 4.13.20 [ 100192 ]
            Julien Rey made changes -
            Link New: This issue is related to JSDSERVER-11964 [ JSDSERVER-11964 ]
            Alex Cooksey made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 659314 ]
            Justin W. made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 627428 ]
            Alex Cooksey made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 574572 ]
            Kunal Kanojia made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            Alex Cooksey made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 574572 ]
            SET Analytics Bot made changes -
            UIS Original: 68 New: 61
            SET Analytics Bot made changes -
            UIS Original: 75 New: 68
            SET Analytics Bot made changes -
            UIS Original: 61 New: 75

              bornatowski Bartosz Ornatowski
              bb910e3a9598 Veenit Doshi
              Affected customers:
              2 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: