-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Customer Portal - Requests
-
None
-
3
-
Severity 3 - Minor
Issue Summary
Inconsistency of the returned values of multi-line text field between work items created from GIC and a portal.
Steps to Reproduce
- Create Jira Service Management project
- Create custom field "type: Text field(multi-line)" and add it to Request type.(ex. create: customfield_xxxxx)
- Set the renderer of the field to a default text renderer
- Create a work item on Agent View(GIC) with leaving custom field blank
- Open a Portal and create a request with leaving custom field blank
Expected Results
The work item which created on both Portal and GIG, custom field value should be same.
If the work item was created with leaving custom field blank, custom field should be null or blank.
Actual Results
The work item which created on Portal, custom field value include values as following.
On the other hand, the ticket created on GIG, customfield_xxxxx is null or missing.
via Portal
XML file view
<customfield id="customfield_xxxxx" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
REST API view
"customfield_XXXXX": { "type": "doc", "version": 1, "content": [ { "type": "paragraph" } ] },
via GIG(Agent View)
XML file view: customfield_xxxxx is missing
REST API view:
"customfield_xxxxx": null,
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.