When I Open a Filter Results in Excel, Some Fields Do Not Export with Proper Values

[ian.silver]

I have a filter to display a selection of tickets from a JSM project.  It works as expected, displaying all chosen columns, including custom fields for Affected Services (from our service registry) and Linked Assets (from our Device42 integration):

However, when I click on the Open in Excel button...

The resulting Excel workbook displays error messages in those custom field cells:

I don't think this is necessarily important, but here are screenshots of the field definitions as well:

When I use the export button and choose CSV, I get a value, but not the human-readable: value:

Is this a known issue?  Or am I doing something wrong?  I'm stumped!

[Hannes Obweger - JXL for Jira]

Hi @ian.silver

it indeed seems like both these fields are not correctly implemented for the Excel export. The Affected services field is owned by Atlassian, so you could consider filing a bug about that. For the other field: Is that a 3rd party field? Or is that the built-in Assets objects custom field?

One thing that may be worth trying is to check out some solutions from the Atlassian Marketplace. There's quite a few dedicated export apps, and I myself happen to work on an app - JXL for Jira - that at least exports the Affected services field nicely; for the other field, that depends on the exact implementation.

This is how this looks in action:

... and this is the export:

Another advantage is that you can export any number of issues in one go.

Any questions just let me know,

Best,

Hannes

[ian.silver]

Thanks for the response Hannes.

Atlassian has informed me that this is not a bug but a feature request as they have not yet fully integrated the old Insight product into Assets.

Add the ability to export Insight object field using Excel

The linked assets field we are using is through an integration to another product - Device 42.

I will take a look your app.  It could be a particularly good fit if you also supported the linked-assets filed export.

Smiles,

Ian

[ian.silver]

@Hannes Obweger - JXL for Jira , I'm picking this up again, and wondering if your app would support the proper export of the custom field values we have for Linked assets.

As you noted, this is from a 3rd party integration and is populated within JSM via an API connection to our instance of Device42.

[Hannes Obweger - JXL for Jira]

Hi @ian.silver,

sorry for the late reply!

I'm still figuring out your exact setup, but from I understand, the Linked assets wouldn't currently work in JXL: 3rd party custom fields have their own, specific implementations, and we haven't done the integration with Device42. There might be a way to do that relatively easily, but I'm still talking to Atlassian to figure out if this is possible or not. I'll keep you posted when I know more.

The other fields - Affected services - would work perfectly fine though.

Sorry I don't have better news right now,

Best,

Hannes

[Hannes Obweger - JXL for Jira]

@ian.silver, please also feel free to get in touch here anytime to discuss things in more detail!