Details
-
Suggestion
-
Resolution: Fixed
-
None
-
None
Description
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"
]
}
]
}
}
]
}
Attachments
Issue Links
- relates to
-
- Closed