[JSDSERVER-2001] Full access to SLA data via REST API

Type: Suggestion
Resolution: Fixed
Fix Version/s: None
Component/s: API and Integrations
Labels:
None

Feedback Policy:

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.

Currently, rest/servicedesk/1/sla/field/all/data/sla resource provides information like this excerpt:

{
    "metricValues": [
        {
            "customFieldId": 10001,
            "customFieldName": "Time to resolution",
            "ongoingCycle": {
                "elapsedTime": 334993181,
                "goalId": 2,
                "hasFailed": true,
                "isPaused": false,
                "startTime": 1433461410269
            }
        }
    ]
}

It doesn't provide enough data for a remote agent to reproduce the behavior on the server side, which is needed to build an offline-capable app for Service Desk.

We suggest to provide a "raw" REST API (say, rest/servicedesk/1/sla/field/all/data/sla-raw) that exposes the internal structure of SLA like this:

{
    "metricValues": [
        {
            "completeSLAData": [],
            "customFieldId": 10001,
            "customFieldName": "Time to resolution",
            "metricId": 1,
            "ongoingSLAData": {
                "goalId": 2,
                "paused": false,
                "startTime": 1433461410269
            },
            "timeline": {
                "events": [
                    {
                        "date": 1433461410269,
                        "types": [
                            "START"
                        ]
                    }
                ]
            }
        }
    ]
}

relates to

JSDCLOUD-2001 Full access to SLA data via REST API

Closed

Charlie Marriott made changes - 04/Mar/2021 3:58 AM

Resolution	Original: Done [ 17 ]	New: Fixed [ 1 ]
Status	Original: Closed [ 6 ]	New: Closed [ 6 ]

Katherine Yabut made changes - 19/Sep/2019 5:56 AM

Workflow	Original: JAC Suggestion Workflow [ 3011816 ]	New: JAC Suggestion Workflow 3 [ 3649426 ]
Status	Original: RESOLVED [ 5 ]	New: Closed [ 6 ]

Owen made changes - 21/Nov/2018 5:43 AM

Workflow

Original: Confluence Workflow - Public Facing v4 [ 2665246 ]

New: JAC Suggestion Workflow [ 3011816 ]

Owen made changes - 27/Apr/2018 12:21 AM

Workflow	Original: JSD Suggestion Workflow - TEMP [ 2324533 ]	New: Confluence Workflow - Public Facing v4 [ 2665246 ]
Status	Original: Closed [ 6 ]	New: Resolved [ 5 ]

Katherine Yabut made changes - 22/Jun/2017 5:54 AM

Workflow

Original: JSD Suggestion Workflow [ 2053665 ]

New: JSD Suggestion Workflow - TEMP [ 2324533 ]

Katherine Yabut made changes - 31/May/2017 12:30 AM

Workflow

Original: JSD Suggestion Workflow - TEMP [ 2048832 ]

New: JSD Suggestion Workflow [ 2053665 ]

Katherine Yabut made changes - 31/May/2017 12:25 AM

Workflow

Original: JSD Suggestion Workflow [ 1280569 ]

New: JSD Suggestion Workflow - TEMP [ 2048832 ]

jonah (Inactive) made changes - 02/Apr/2017 11:47 AM

Description

Original: Currently, {{rest/servicedesk/1/sla/field/all/data/sla}} resource provides information like this excerpt:
{code}
{
    "metricValues": [
        {
            "customFieldId": 10001,
            "customFieldName": "Time to resolution",
            "ongoingCycle": {
                "elapsedTime": 334993181,
                "goalId": 2,
                "hasFailed": true,
                "isPaused": false,
                "startTime": 1433461410269
            }
        }
    ]
}
{code}

It doesn't provide enough data for a remote agent to reproduce the behavior on the server side, which is needed to build an offline-capable app for Service Desk.

We suggest to provide a "raw" REST API (say, {{rest/servicedesk/1/sla/field/all/data/sla-raw}}) that exposes the internal structure of SLA like this:

{code}
{
    "metricValues": [
        {
            "completeSLAData": [],
            "customFieldId": 10001,
            "customFieldName": "Time to resolution",
            "metricId": 1,
            "ongoingSLAData": {
                "goalId": 2,
                "paused": false,
                "startTime": 1433461410269
            },
            "timeline": {
                "events": [
                    {
                        "date": 1433461410269,
                        "types": [
                            "START"
                        ]
                    }
                ]
            }
        }
    ]
}
{code}

New: {panel:bgColor=#e7f4fa}
  *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-2001].
  {panel}

Currently, {{rest/servicedesk/1/sla/field/all/data/sla}} resource provides information like this excerpt:
{code}
{
    "metricValues": [
        {
            "customFieldId": 10001,
            "customFieldName": "Time to resolution",
            "ongoingCycle": {
                "elapsedTime": 334993181,
                "goalId": 2,
                "hasFailed": true,
                "isPaused": false,
                "startTime": 1433461410269
            }
        }
    ]
}
{code}

It doesn't provide enough data for a remote agent to reproduce the behavior on the server side, which is needed to build an offline-capable app for Service Desk.

We suggest to provide a "raw" REST API (say, {{rest/servicedesk/1/sla/field/all/data/sla-raw}}) that exposes the internal structure of SLA like this:

{code}
{
    "metricValues": [
        {
            "completeSLAData": [],
            "customFieldId": 10001,
            "customFieldName": "Time to resolution",
            "metricId": 1,
            "ongoingSLAData": {
                "goalId": 2,
                "paused": false,
                "startTime": 1433461410269
            },
            "timeline": {
                "events": [
                    {
                        "date": 1433461410269,
                        "types": [
                            "START"
                        ]
                    }
                ]
            }
        }
    ]
}
{code}

jonah (Inactive) made changes - 02/Apr/2017 11:47 AM

Link

New: This issue relates to ~~JSDCLOUD-2001~~ [ ~~JSDCLOUD-2001~~ ]

Grégory Joseph (Inactive) made changes - 12/Aug/2016 6:32 AM

Resolution		New: Done [ 17 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

Assignee:: Unassigned

Reporter:: Igor Sereda [ALM Works]

Votes:: 1 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 19/Jun/2015 1:49 PM

Updated:: 04/Mar/2021 3:58 AM

Resolved:: 04/Mar/2021 3:58 AM

Jira Service Management Data Center

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates

Backbone Issue Sync