Xporter should integrate with Elements Connector App

Description

Xporter should integrate with the Elements Connect app. Currently, users cannot export data from Elements Connect custom fields to documents generated by Xporter. When an export is triggered, these fields either appear blank or do not render the fetched external data correctly.

User friction

• Users cannot generate complete documentation because crucial external data managed by Elements Connect is missing from the exported files.
• Many organizations migrating from Jira Data Center to Jira Cloud rely on this integration as it was present in Xporter DC.
• Because automated or seamless exports aren't possible with these fields, teams face significant friction trying to gather reports.

Steps to reproduce (right now) / Actual Result:

• Create a Jira issue containing an Elements Connect custom field that dynamically pulls data from an Elements Connector app

• Ensure the field is populated with data and visible on the Jira issue view.

• Attempt to export the issue using an Xporter template that references the Elements Connect field mapping.

• The exported document (Word, PDF, Excel) leaves the field blank.

IMPACT{}

What would improve if solved:

• Users will be able to export rich, external data from the Element connector app.
• Eliminates a major blocker for Cloud customers moving from Data Center to Jira Cloud who heavily rely on the Elements Connector app Data for Daily export

Impact on stakeholders:

• The exported file have the Blank fields, which makes the report inaccurate.

Current workaround:

• There is no workaround for now, but manually copy and paste the data from Jira issue screen into the Export file.

CONTEXT & EXAMPLES:

Concrete example: A company uses Elements Connect to pull data details from this app to Jira Cloud Custom field for major work and then export using the Xporter, which gives the value blank in the export file, which is incomplete data.

Workaround risk

• As there is no work around so no risk.