Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-3306

Include breachedDate in completed SLA cycles result in JIRA issue REST API

    XMLWordPrintable

Details

    • 1

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

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

      I am Lauma from eazyBI development team. Our common customer is asking if it would be possible to reflect in eazyBI report which was the Assignee of issue at the moment of SLA breach.

      We get the SLA status information from JIRA Issue JSON result (JIRA_BASE_URL/rest/api/latest/issue/KEY-NN), the SLA custom field attributes

      "customfield_10104": {
"completeCycles": [
{
"breached": true,
"goalTime": 14400000,
"elapsedTime": 46551416356,
"calendarName": "24/7 Calendar (Default)",
"startDate": 1390225933243,
"stopDate": 1436777349599
},
{
"breached": false,
"goalTime": 14400000,
"elapsedTime": 195348,
"calendarName": "24/7 Calendar (Default)",
"startDate": 1453104436042,
"stopDate": 1453104631390
}
],
"ongoingCycle": {
"goalId": 4,
"startDate": 1453211159567,
"elapsedTime": 9961,
"breached": false,
"paused": false,
"remainingTime": 14390039,
"breachedDate": 1453225559567
}
}

      Currently we cannot detect the Assignee at breached moment and import it to eazyBI as the breachedDate is displayed only in an ongoing cycle

      "ongoingCycle": {
"goalId": 4,
"startDate": 1453211159567,
"elapsedTime": 9961,
"breached": false,
"paused": false,
"remainingTime": 14390039,
"breachedDate": 1453225559567
}

      This is the date of when the ongoing cycle will be breached.

      But in completed cycles there is no breachedDate 

      "completeCycles": [
{
"breached": true,
"goalTime": 14400000,
"elapsedTime": 46551416356,
"calendarName": "24/7 Calendar (Default)",
"startDate": 1390225933243,
"stopDate": 1436777349599
}

      So for completed cycles we cannot find when the cycle was breached and detect who was the assignee of issue at that moment. As there can be various calendars used, the calculation from startDate, goalTime and elapsedTime might not be entirely correct.

      Let me know if this would be possible to implement for future.

      Attachments

        Issue Links

          is duplicated by

          Suggestion - JSDCLOUD-3881 Expose breach date/time for completed SLA cycles

          • Closed
          is related to

          Suggestion - JSDSERVER-3306 Include breachedDate in completed SLA cycles result in JIRA issue REST API

          • Closed

          Suggestion - JSDCLOUD-9973 Add the ability to retrieve SLA data via API

          • Gathering Interest

          Suggestion - JSDCLOUD-11020 REST API endpoint to create edit or delete projects SLA

          • Gathering Interest
          mentioned in

          Page Loading...

          relates to

          SDECO-112 Loading...

          Activity

            People

              Unassigned Unassigned
              lauma.cirule Lauma Cīrule
              Votes:
              11 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: