-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
4.17.0, 4.20.2, 5.2.0
-
4
-
Severity 2 - Major
-
4
-
Issue Summary
Insight custom fields values are not exported with data pipeline feature
Steps to Reproduce
- Create some Insight custom fields and create some Jira issues containing values filled for those Insight custom fields
- 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
- links to
[JSDSERVER-10933] Insight custom fields values are not exported with data pipeline feature
How can this be rated "low" priority? The data center feature of exporting data to do reporting misses out fields that are part of your own product. 99% of the reporting our users want to do will be based on the CI that is selected from Insight, making the data pipeline useless.
I'm probably going to have to write something in scriptrunner to get around this, since this ticket has been open for 2 years now.
This feature is critical to our team, however also unusable without being able to pull out asset object and referenced asset object custom fields, as we rely on data in many of our asset models.
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.