-
Type:
Bug
-
Resolution: Timed out
-
Priority:
Low
-
Component/s: Work Item - Backend - Rich Text
-
4
-
Severity 3 - Minor
-
0
Summary
Updating issue values such as description or custom fields is not working as expected:
- The history tab is not handling the ADF and displaying the full json content of the response.
- Custom field values are not populated correctly.
- The jiraissuetokens table is not being updated meaning values populated are not searchable.
Steps to Reproduce
- Add a screen to a transition
- Make a call to */rest/api/3/issue/
{issueid}
/transitions* to transition an issue with field updates like below:
{ "transition": { "id": 21 }, "fields": { "description": { "version": 1, "type": "doc", "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": "this is my description now" } ] } ] }, "customfield_10054": "http://www.ramblingvapers.com", "customfield_10051": { "version": 1, "type": "doc", "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": "root cause" } ] } ] }, "customfield_10052": { "version": 1, "type": "doc", "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": "some text" } ] } ] }, "customfield_10053": { "version": 1, "type": "doc", "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": "texty text" } ] } ] } } }
Expected Results
The custom field values are populated correctly.
The values are included in the jiraissuetokens table.
This history displays the values correctly:
Actual Results
The custom field values are not populated correctly or at all.
The values are not added to the jiraissuetokens table.
This history displays full ADF json:
Workaround
Currently the best workaround is to use the API V2 endpoint: The Jira Cloud platform REST API V2: Transition Issue
- was cloned as
-
JRACLOUD-71992 Transitioning issue using REST API V3 without specifying fields wipes current field data.
-
- Closed
-