Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-10056

Add the ability to export Assets field value instead of internal key during CSV export

XMLWordPrintable

    • 570

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    • Hide

      Hello Team 👋 ,

      We are thrilled to announce the release of a fix for this critical issue. This update addresses the csv export issue and ensures smoother operations in exporting your Jira data.

      Here’s what we have done:

      • Additional Data Column: We’ve added a new column in the export CSV that displays the label of the object, providing meaningful information to teams utilising these export files.
      • Retention of Internal IDs: To ensure continuity and prevent disruption in your import processes, we have retained the internal IDs in the export files. Please continue to use these IDs for importing Jira issues.
      • Export Limit Adjustment: The maximum number of objects per export is now set at 1000. We believe this limit will cover the majority of your export needs. However, for large-scale exports, we strongly recommend dividing them into batches.
      • Rate Limits and Timeouts: Due to CMDB rate limits and potential Jira timeouts, we reiterate our recommendation to perform exports in batches, particularly when dealing with large volumes of tickets.

      Supported and Unsupported Formats:

      • Supported Formats: The fix has been applied to the following export formats: Print Details, XML, Word, RSS, and Excel.
      • Unsupported Formats: Currently, we are unable to extend this fix to Google Sheets, Print Lists, and HTML exports. We understand this may impact some teams, and we encourage you to provide feedback or log a ticket, for Print Lists please feel free to vote and follow this ticket JSDCLOUD-13028. And for issues concerning HTML or Google Sheets exports, please log a request through the usual channels.

      We appreciate your patience and cooperation as we worked to resolve this complex issue. Your feedback is invaluable to us, and we look forward to continually enhancing your experience with our platform.

      Warm regards 🙏

      Mohamed Hassan | Product Manager, JSM Assets

      Show
      Hello Team 👋 , We are thrilled to announce the release of a fix for this critical issue. This update addresses the csv export issue and ensures smoother operations in exporting your Jira data. Here’s what we have done: Additional Data Column:  We’ve added a new column in the export CSV that displays the label of the object, providing meaningful information to teams utilising these export files. Retention of Internal IDs:  To ensure continuity and prevent disruption in your import processes, we have retained the internal IDs in the export files. Please continue to use these IDs for importing Jira issues. Export Limit Adjustment:  The maximum number of objects per export is now set at 1000. We believe this limit will cover the majority of your export needs. However, for large-scale exports, we strongly recommend dividing them into batches. Rate Limits and Timeouts:  Due to CMDB rate limits and potential Jira timeouts, we reiterate our recommendation to perform exports in batches, particularly when dealing with large volumes of tickets. Supported and Unsupported Formats: Supported Formats:  The fix has been applied to the following export formats: Print Details, XML, Word, RSS, and Excel. Unsupported Formats:  Currently, we are unable to extend this fix to Google Sheets, Print Lists, and HTML exports. We understand this may impact some teams, and we encourage you to provide feedback or log a ticket, for Print Lists please feel free to vote and follow this ticket  JSDCLOUD-13028 . And for issues concerning HTML or Google Sheets exports, please log a request through the usual channels. We appreciate your patience and cooperation as we worked to resolve this complex issue. Your feedback is invaluable to us, and we look forward to continually enhancing your experience with our platform. Warm regards 🙏 Mohamed Hassan | Product Manager, JSM Assets

      Problem

      During the Assets export process, the CSV output does not display the actual Assets objects names for the Insight object custom fields. Instead, those are represented as an internal key in format <WorkspaceID>:<ObjectKeyNumber>

      Suggested Solution

      After export, CSV outputs should show Assets object names or object keys in the columns for Insight object custom fields.

      Why This Is Important

      Unable to get complete data during exports impacting management reports

      Workaround

      Process the exports with another tool and make a GET request to each object to get further details, eg:

      https://api.atlassian.net/jsm/insight/workspace/<workspace-id>/v1/object/<object-id>{}

        1. screenshot-1.png
          screenshot-1.png
          242 kB

              90325da67d46 Mohamed Hassan
              cf3a9e2a2246 Diptajeet Datta
              Votes:
              396 Vote for this issue
              Watchers:
              192 Start watching this issue

                Created:
                Updated:
                Resolved: