Hi there, this might have been what was asked earlier in the thread: If from the search results I wish to download the results to Microsoft Excel via the Apps dropdown (as below) then for any column based on an Asset, you still simply see [no field found]. This happens regardless of whether you have more or less than 1000 results returned. The value in exporting results like this is that it will only export the fields defined in the search/filter, as opposed to using default columns, which is a fairly large UX problem for us. Is there an intention of finishing this feature and bringing some sort of behavioural parity between these two export mechanisms?

Hi 90325da67d46 

Thanks fdor the reply, i haven't eny inconvenience to share the screenshot

but i cant add it to my comment, so i'll send you the screenshot by email.

Cheers!

Hi a6d74b6386c9 - What do you mean by the apps section? Feel free to email me if you don't want to share on the ticket (mhassan@atlassian.com)

Thanks,

Mohamed

Hello 90325da67d46 

I've just checked it and for the apps section and i see that these label values from asset custom fields aren't in the reports,

Could you say to us if this part is on developing or it isn't in the scope for this ticket?

Kind regards, 

Hello Team 👋 ,

We are thrilled to announce the release of a fix for this critical issue. This update addresses the csv export issue and ensures smoother operations in exporting your Jira data.

Here’s what we have done:

• Additional Data Column: We’ve added a new column in the export CSV that displays the label of the object, providing meaningful information to teams utilising these export files.
• Retention of Internal IDs: To ensure continuity and prevent disruption in your import processes, we have retained the internal IDs in the export files. Please continue to use these IDs for importing Jira issues.
• Export Limit Adjustment: The maximum number of objects per export is now set at 1000. We believe this limit will cover the majority of your export needs. However, for large-scale exports, we strongly recommend dividing them into batches.
• Rate Limits and Timeouts: Due to CMDB rate limits and potential Jira timeouts, we reiterate our recommendation to perform exports in batches, particularly when dealing with large volumes of tickets.

Supported and Unsupported Formats:

• Supported Formats: The fix has been applied to the following export formats: Print Details, XML, Word, RSS, and Excel.
• Unsupported Formats: Currently, we are unable to extend this fix to Google Sheets, Print Lists, and HTML exports. We understand this may impact some teams, and we encourage you to provide feedback or log a ticket, for Print Lists please feel free to vote and follow this ticket JSDCLOUD-13028. And for issues concerning HTML or Google Sheets exports, please log a request through the usual channels.

We appreciate your patience and cooperation as we worked to resolve this complex issue. Your feedback is invaluable to us, and we look forward to continually enhancing your experience with our platform.

Warm regards 🙏

Mohamed Hassan | Product Manager, JSM Assets

This is at least the third example of a function that my organization used on-premise in Datacenter that doesnt work in Cloud.   Each time there is a suggestion that has been opened for 12+ months with no traction. 

You can't promote yourself as an asset management tool if your OOB capabilities dont allow for reports to be generated.   JSM Assets has effectively ZERO reporting visible to anyone by a Site Admin.   Now I find out that even filters using Assets data can't be exported.   

This is a problem, as people have been reporting for over a year.   Is it a technical limitation or simply something Atlassian doesn't plan to do?

Basically good, that there is a workaround, but at least for our size this addon is not free anymore.
As Atlassian is not able to provide basic functionality like this for a lot of money the get from us all and even has no priority to fix it, we surely don't invest money for addons to fix their bugs by workarounds.

But as others seems to be able to do what Atlassian itself can't handle, Atlassian could take over the costs for the workaround for all affected customers or pay the addon producer to support them fixing the problem. But I guess nothing of that will happen.

I found a workaround!   use the Better Excel Exporter app (by Midori) and use the 'field-helper-tool.groovy' template. it works!

+1 for this !   It doesn't seem like this should be a suggestion, it should be a fix.

It is not working in Cloud (with JSM Assets) the same way it works in Server (with the Assets app)

As an Atlassian Partner - this is essential for our customers who export Asset Fields and use them in other systems.     This was working in Server,  we need it to work in Cloud as we move forward with a focus on moving everyone to Atlassian Cloud 

+1
Please, essential to generate reports. We cannot have the same reports we had before migrating to cloud.
 
Thank you.