Jira Cloud for Excel (official) pluggin for reporting

[Florin]

So for a bit of context. We are using the "Jira Cloud for Excel (official)" plugin for reporting, meaning that we export all the issues via this plugin.  We don't use the Jira native export option as it cannot get all the tickets (we have thousands).

We report only the custom fields we need.

The problem when using this plugin is that these 2 custom fields appear blank or "no field found" in Excel. This is not good for us. This is when exporting as XLSX.

When exporting as CSV the fields are not blank anymore nor with "no field found", but they are now with the object(asset) ID key. This is a bit better as we have a value, but we have a rule in place to copy the info as plain text in the field.

This is what we see in Jira when searching for the 2 custom fields.

This is what we get when exporting now.

I am wondering if anyone encountered this issue. If there is a workaround. If there is some way better for us to export these values. Any help is much appreciated.

Thank you for your time.

[Florin · Accepted solution]

Got an answer from Support. I will post it here in case there are others facing this issue.

I see that you are using our Jira Cloud for Excel plugin and seeing that asset custom fields are not exporting data at all - showing "no field found" as a result.

This is because asset fields are not yet supported by this plugin:
https://jira.atlassian.com/browse/API-491

As a workaround, you can create an Automation rule that on the field update of each asset field, it passes the value to a text field which can be exported by the plugin.

The smartvalue to use on the edit issue action for the text field should follow this format:

{{"Name of Customfield"."Name of the attribute you want to have the value on export"}}

[Csaba Vertessy]

And after Atlassian changed the policy for Automation rules they are expecting from us to fix the bugs...