Details
-
Suggestion
-
Resolution: Unresolved
-
114
-
2
-
Description
NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.
Problem Solution:
At the moment, when we run a GET REST API to get a request type details, the response will be shown like below:
GET /rest/servicedeskapi/servicedesk/{serviceDeskId}/requesttype
{
"id": "18",
"_links": {
"self": "http://xxxxxx/rest/servicedeskapi/servicedesk/1/requesttype/18"
},
"name": "Monitor",
"description": "",
"helpText": "",
"serviceDeskId": "1",
"groupIds": [
"1"
],
"icon": {
"id": "10532",
"_links": {
"iconUrls": {
"48x48": "http://xxxxx/secure/viewavatar?avatarType=SD_REQTYPE&size=large&avatarId=10532",
"24x24": "http://xxxxx/secure/viewavatar?avatarType=SD_REQTYPE&size=small&avatarId=10532",
"16x16": "http://xxxxx/secure/viewavatar?avatarType=SD_REQTYPE&size=xsmall&avatarId=10532",
"32x32": "http://xxxxx/secure/viewavatar?avatarType=SD_REQTYPE&size=medium&avatarId=10532"
}
}
}
}
From here, we could not actually find the key of the request type that is being used for JIRA when storing the Customer Request Type Custom field value in the database.
Suggested Solution:
To include the key in the response or better adding the lowercase project key at the front as how it is in the customfieldvalue table.
Workaround
See below KB article for a workaround. However, please take into account that this is not supported and it may stop working without any previous notice:
Attachments
Issue Links
- is related to
-
- Gathering Interest
- is resolved by
-
SHIELD-4241 Loading...
- mentioned in
-