Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-6071

Service Desk 'Customer Request Type' field value does not show in exported file in HTML format

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 4.2.0
    • 3.15.1
    • Issue View

      Summary

      Service Desk 'Customer Request Type' field value does not show in exported file in HTML format

      Steps to Reproduce

      1. Go to Issues > Search for issues
      2. Filter Service Desk project type issues
      3. Add 'Customer Request Type' as a column
      4. Click Export > HTML (Current Fields)

      Expected Results

      Customer Request Type values get exported

      Actual Results

      Customer Request Type are blank in the export HTML file

      Workaround

      There is no workaround in regards to HTML format specifically. However, CSV format still contains exported Request Types.

      Note

      Tested this behaviour in Jira versions 7.6.8 (SD 3.9.8) and 7.8.1 (SD 3.11.1) and the behaviour works as expected.

          Form Name

            [JSDSERVER-6071] Service Desk 'Customer Request Type' field value does not show in exported file in HTML format

            Nakul Razdan made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 429525 ]
            Nakul Razdan made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 429525 ]
            Przemyslaw Czuj (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]

            Radek Dostál added a comment -

            The release version is marked for 4.2 however I am seeing 'Customer Request Type' value being exported to HTML on JSW 7.13.2 and JSD 3.16.2.

             

            On the other hand, I am not seeing any bug report with regard to .xml export. In fact, that's where the Customer Request Type value is a white space in our case, e.g.:

             <customfield id="customfield_13812" key="com.atlassian.servicedesk:vp-origin">
 <customfieldname>Customer Request Type</customfieldname>
 <customfieldvalues> </customfieldvalues>                      <!-- see the white space -->
 </customfield>

             

             

            Does this release fix the .xml export?
             

            Radek Dostál added a comment - The release version is marked for 4.2 however I am seeing 'Customer Request Type' value being exported to HTML on JSW 7.13.2 and JSD 3.16.2.   On the other hand, I am not seeing any bug report with regard to .xml export. In fact, that's where the Customer Request Type value is a white space in our case, e.g.: <customfield id= "customfield_13812" key= "com.atlassian.servicedesk:vp-origin" > <customfieldname> Customer Request Type </customfieldname> <customfieldvalues> </customfieldvalues> <!-- see the white space --> </customfield>     Does this release fix the .xml export?  
            Elton Santos made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 422793 ]
            Elton Santos made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 422783 ]
            Elton Santos made changes -
            Status Original: In Progress [ 3 ] New: Waiting for Release [ 12075 ]
            Elton Santos made changes -
            Status Original: Needs Triage [ 10030 ] New: In Progress [ 3 ]
            Elton Santos made changes -
            Fix Version/s New: 4.2.0 [ 85904 ]
            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2873488 ] New: JAC Bug Workflow v3 [ 3126686 ]
            Status Original: Untriaged [ 11672 ] New: Needs Triage [ 10030 ]

              Unassigned Unassigned
              mfilipan Marko Filipan
              Affected customers:
              2 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: