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

Insight custom fields values are not exported with data pipeline feature

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 4.17.0, 4.20.2, 5.2.0
    • Assets - Core experiences

      Issue Summary

      Insight custom fields values are not exported with data pipeline feature

      Steps to Reproduce

      1. Create some Insight custom fields and create some Jira issues containing values filled for those Insight custom fields
      2. Launch the data pipeline export with the rest api and observe that the issue_fields_XXXXXXXXXXX.csv file in the data pipeline export folder does not contains Insight custom fields values for existing issues.

      Note: Export file contains Advanced Roadmap custom fields values and Jira native custom fields values

      Expected Results

      Data pipeline export should contains Insight custom fields

      Actual Results

      Data pipeline export does not contains Insight custom fields

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

          Form Name

            [JSDSERVER-10933] Insight custom fields values are not exported with data pipeline feature

            Marc Dacanay made changes -
            Labels New: ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 955357 ]
            SET Analytics Bot made changes -
            UIS Original: 2 New: 4
            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 4
            SET Analytics Bot made changes -
            UIS Original: 4 New: 2
            SET Analytics Bot made changes -
            UIS Original: 5 New: 4
            SET Analytics Bot made changes -
            UIS Original: 4 New: 5
            SET Analytics Bot made changes -
            UIS Original: 5 New: 4
            SET Analytics Bot made changes -
            UIS Original: 4 New: 5

            Amos added a comment -

            We ended up having to use a combination of webhooks and asset automations to achieve our BI requirements. Our data models are intrinsicly linked to assets. We also discovered that webhooks don't support assets (like they do in cloud - go figure), so we've had to do something like 24 automation rules to POST to a logstash/opensearch endpoint.

            The sustainment overhead on our side for what should be simply an available feature is extremely frustrating. It also means having to recreate the data model on the other side once out of the Jira environment.

            Amos added a comment - We ended up having to use a combination of webhooks and asset automations to achieve our BI requirements. Our data models are intrinsicly linked to assets. We also discovered that webhooks don't support assets (like they do in cloud - go figure), so we've had to do something like 24 automation rules to POST to a logstash/opensearch endpoint. The sustainment overhead on our side for what should be simply an available feature is extremely frustrating. It also means having to recreate the data model on the other side once out of the Jira environment.

              Unassigned Unassigned
              tmarchionni@atlassian.com Tiziana Marchionni
              Affected customers:
              8 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated: