-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Low
-
Component/s: Forge and Connect
-
None
-
Severity 3 - Minor
Summary
Previously in JIRA (v1000.892.1) when calling endpoint https://instance.atlassian.net/rest/api/2/issue/issuekey
The return for the organization field of an issue in JIRA Service desk was:
"customfield_10001": null, "customfield_10002": [ "exampleorganization" ], "customfield_10006": null,
In JIRA 1000.962 the response is coming with additional details
"customfield_10001": null, "customfield_10002": [ { "_links": { "self": "https://instance.atlassian.net/rest/servicedeskapi/organization/1" }, "id": "1", "name": "exampleorganization" } ], "customfield_10006": null,
The problem is that this change was not communicated and customers using scripts expecting the old pattern now need to change their scripts in order to fully work with JIRA API.
Steps to Reproduce
Call this endpoint for an issue in service desk with an organization in custom field.
Expected Results
Receive the response as following
"customfield_10001": null, "customfield_10002": [ "exampleorganization" ], "customfield_10006": null,
Actual Results
Receiving the organization with
"customfield_10001": null, "customfield_10002": [ { "_links": { "self": "https://instance.atlassian.net/rest/servicedeskapi/organization/1" }, "id": "1", "name": "exampleorganization" } ], "customfield_10006": null,
Workaround
None.
- is caused by
-
JSDCLOUD-4875 Add REST support for setting Organization on a ticket - Cloud
- Closed
- depends on
-
JSDECO-53 Loading...