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

"Customer Request type" field get encoded when exported to CSV

XMLWordPrintable

      NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      Summary

      When the user exports an issue from Service desk to CSV(all fields) the "Customer Request type" do not show the actual name of the request type, instead it shows a code from it.

      Steps to Reproduce

      1. Search for service desk issue that contains not default request types
      2. Click on Export Excel CSV (all fields)

      Expected Results

      On the exported csv, "Customer Request type" field shows the name of the request type.

      Actual Results

      It shows a code from it.

      Take note that the exported value is in the form of: Project_Key/Request_Type_Key

      Workaround

      Run this SQL query from the database:
      NOTE this is written in PostgreSQL syntax and may need to be modified for for your database type:

       select vp."KEY" as project_key, vpf."NAME" as Request_type_Name, vpf."KEY" AS request_type from "AO_54307E_VIEWPORT" vp join "AO_54307E_VIEWPORTFORM" vpf on vpf."VIEWPORT_ID" = vp."ID";

      Then base on the KEY to find the NAME.

        1. Screen Shot 2016-11-21 at 12.08.55 PM.png
          Screen Shot 2016-11-21 at 12.08.55 PM.png
          44 kB

            [JSDSERVER-4520] "Customer Request type" field get encoded when exported to CSV

            Mateusz T made changes -
            Remote Link Original: This issue links to "JSDS-3785 (Bulldog)" [ 416547 ] New: This issue links to "JSMDC-3785 (JIRA Server (Bulldog))" [ 416547 ]
            Edson Araujo made changes -
            Remote Link Original: This issue links to "JSDS-1093 (Bulldog)" [ 424538 ] New: This issue links to "JSMDC-1093 (JIRA Server (Bulldog))" [ 424538 ]

            Rodrigo Baldasso added a comment -

            Hi apetridou, the fix has been deployed to Jira Service Desk 4.4.0 onwards, and accordingly to the compatibility matrix, this version is only compatible with Jira Core 8.3.0 onward.

            Rodrigo Baldasso added a comment - Hi apetridou , the fix has been deployed to Jira Service Desk 4.4.0 onwards, and accordingly to the compatibility matrix , this version is only compatible with Jira Core 8.3.0 onward.

            Athena Petridou [Nimaworks] added a comment -

            Hi,

            This is not fixed. 
            Jira Version 7.9.0 , 8.2.4 

            Athena Petridou [Nimaworks] added a comment - Hi, This is not fixed.  Jira Version 7.9.0 , 8.2.4 
            Siddharth Srivastava made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            SET Analytics Bot made changes -
            UIS Original: 28 New: 32
            SET Analytics Bot made changes -
            UIS Original: 32 New: 28
            SET Analytics Bot made changes -
            UIS Original: 35 New: 32
            SET Analytics Bot made changes -
            UIS Original: 42 New: 35
            SET Analytics Bot made changes -
            UIS Original: 46 New: 42

              siddharth@atlassian.com Siddharth Srivastava
              bcasaroli Bernardo Casaroli (Inactive)
              Affected customers:
              79 This affects my team
              Watchers:
              60 Start watching this issue

                Created:
                Updated:
                Resolved: