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

CSV export contains unreadable Satisfaction data

XMLWordPrintable

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

      Steps to reproduce

      1. Enable Satisfaction for an SD project and Resolve a Request for a Survey to be sent to Reporter
      2. Rate the Survey with a Five-star
      3. Go to Issue Navigator and search for Satisfaction = 5
      4. Edit Columns and display Satisfaction (List view only)
      5. Export the result to CSV (Current fields)

      Expected behavior

      The Satisfaction field in the CSV file contains a readable value of 5

      Actual behavior

      The field contains an unreadable value e.g.:

      com.atlassian.servicedesk.internal.api.customfields.feedback.RequestFeedbackCFValue@d3f24

      Note

      In SD 3.1 with Excel export (CSV is available in SD 3.2), the field is reported not to contain any value in the Excel file

            [JSDSERVER-4334] CSV export contains unreadable Satisfaction data

            Paul Madison added a comment -

            Is the data stored in the database as that ugly string?  Seems odd that I can't get useful data from the APIs.

            com.atlassian.servicedesk.internal.api.customfields.feedback.RequestFeedbackCFValue@d3f24

            Paul Madison added a comment - Is the data stored in the database as that ugly string?  Seems odd that I can't get useful data from the APIs. com.atlassian.servicedesk.internal.api.customfields.feedback.RequestFeedbackCFValue@d3f24

            Marcelo Mella added a comment -

            Any news about this issue?

            Marcelo Mella added a comment - Any news about this issue?

            Mike Shyavitz added a comment -

             Very surprised to see such an absurd limitation for such a critical service desk function. This should have been fixed years ago when first reported. 

            Mike Shyavitz added a comment -  Very surprised to see such an absurd limitation for such a critical service desk function. This should have been fixed years ago when first reported. 

            Zans McLachlan added a comment - - edited

            Supporting a user with this very issue today. Can this please be prioritized on the roadmap? Thanks!

             

            EDIT: as a corollary, we'd also like to include the Feedback Comment in this reporting. As of now, there is no way to produce a report including this without Scriptrunner shennanigans.

            Zans McLachlan added a comment - - edited Supporting a user with this  very issue today. Can this please be prioritized on the roadmap? Thanks!   EDIT: as a corollary, we'd also like to include the Feedback Comment in this reporting. As of now, there is no way to produce a report including this without Scriptrunner shennanigans.

            Leonardo Lagos added a comment -

            Still present in 3.15.3.... horrible... 

            Leonardo Lagos added a comment - Still present in 3.15.3.... horrible... 

            Aron Gombas [Midori] added a comment -

            The app called Better Excel Exporter can export the satisfaction values (and other Service Desk specific custom fields) without any further massaging.

            Use this as a viable workaround while it is fixed in the CSV export.

            (Disclaimer: the app is developed by my team.)

            Aron Gombas [Midori] added a comment - The app called Better Excel Exporter can export the satisfaction values (and other Service Desk specific custom fields ) without any further massaging. Use this as a viable workaround while it is fixed in the CSV export. (Disclaimer: the app is developed by my team.)

            Italo Qualisoni [e-Core] added a comment -

            Please add 3.13.1 in affected version.

            Italo Qualisoni [e-Core] added a comment - Please add 3.13.1 in affected version.

            Italo Qualisoni [e-Core] added a comment -

            This issue has been resolved +1 year ago in Cloud. This is a very annoying bug that makes us and our customers to do Excel macro as workaround.  Please provide us a status about this issue progress!

            Italo Qualisoni [e-Core] added a comment - This issue has been resolved +1 year ago in Cloud. This is a very annoying bug that makes us and our customers to do Excel macro as workaround.  Please provide us a status about this issue progress!

            Jan Cierpisz added a comment -

            Is there a approximate date when it will be fixed?

             

            Jan Cierpisz added a comment - Is there a approximate date when it will be fixed?  

            Huw Evans added a comment -

            Any plans to implement this — it's likely a 5 second fix to add a `toString` method

            Huw Evans added a comment - Any plans to implement this — it's likely a 5 second fix to add a `toString` method

              kkanojia Kunal Kanojia
              vdung Andy Nguyen (Inactive)
              Affected customers:
              83 This affects my team
              Watchers:
              46 Start watching this issue

                Created:
                Updated:
                Resolved: