-
Bug
-
Resolution: Fixed
-
Low
-
2.5.6, 3.9.1, 4.0.2
-
4
-
Severity 3 - Minor
-
1
-
When searching for issues in a JIRA with Service Desk, you can select the "Customer Request Type" (or SLA, or Request Participant) custom field as a column. This displays correctly.
If you now export as xml, then the value for the "Customer Request Type" field is not included in the generated xml.
<customfield id="customfield_10000" key="com.atlassian.servicedesk:vp-origin"> <customfieldname>Customer Request Type</customfieldname> <customfieldvalues></customfieldvalues> </customfield>
From our Confluence, we search JIRA/SD and rely on the xml export to process the output using xslt. Because the "Customer Request Type" is not included in the xml, we cannot display it on our page.
It also means the field cannot be displayed in Confluence using the JIRA issues macro. See CONF-38703.
- is related to
-
JSDSERVER-581 Service Desk SLA Custom Field values doesn't show in XML format
-
- Closed
-
-
CONFSERVER-38703 Issue Macro Does Not Shows Service Desk's Custom Field
-
- Gathering Impact
-
[JSDSERVER-2357] Service Desk 'Customer Request Type', 'SLA', 'Request Participants' custom field values do not show in XML format
Remote Link | Original: This issue links to "Page (Confluence)" [ 429626 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 429626 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 422864 ] |
UIS | Original: 2 | New: 1 |
Remote Link | New: This issue links to "Page (Confluence)" [ 421397 ] |
UIS | Original: 1 | New: 2 |
UIS | Original: 3 | New: 1 |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304596 ] | New: JAC Bug Workflow v3 [ 3126020 ] |
Status | Original: Awaiting Release [ 11372 ] | New: Waiting for Release [ 12075 ] |
Fix Version/s | New: 4.1.1 [ 85903 ] | |
Fix Version/s | New: 4.2.0 [ 85904 ] |