-
Suggestion
-
Resolution: Unresolved
-
None
While exporting the Assets objects field using the add-on Jira Cloud for Excel (option Open in Excel) or Jira Cloud for Google Sheets (option Open in Google Sheets), it shows [no field found]
Suggested Solution
Add the ability to export Assets objects field value using Excel or Google Sheets export.
Workaround
As a workaround, you can use automation to copy the value of an Insight field to a Jira text field. Please check the section Edit Issue in this link which may help.
- duplicates
-
- Closed
- is duplicated by
-
- Closed
- is related to
-
JSDCLOUD-11838 Printing or exporting from the Issue View prints empty Insight custom fields even when there is a value set
-
- Closed
-
- relates to
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[API-491] Add the ability to export Assets objects field using Excel and Google Sheets
+1 as we're using exports to Excel quite often and having to create a separate lookup for assets is inefficient
please make this work. I dont understand why this wouldn't be a default feature.
Very interested in making this a feature. Assets should be exportable as normal during reports..
This would be a very useful feature, as of right now. Utilizing a spreadsheet is the easiest way to audit asset records and correlate multiple schemas and add relational links that are quite difficult to do in the cloud instance if not impossible at the moment. Lookup tables and queries are way easier and more straight forward do with a spreadsheet. The reporting feature is also quite limited and reduces visibility and granularity of the report the more details one wants to display, (i.e I see less records the more information I want to see in the report)
Google Sheets enhances the ability to create and modify bulk updates immensely with an ease that currently is limited in nature right now with the current interface and for someone with limited programing skills creating these enhancements in this platform requires a level of programing knowledge skill higher than most managers are capable of or want to be aware of. For an IT admin, this should be drag and drop, drop dead easy to accomplish.
Using forms to update asset objects is way too difficult a task to achieve with efficiency which is why exporting the records to a spreadsheet and then use it to update bulk records rather than create a workflow that is fret with workaround after work around to implement. With little to no tools to assist with the quality or test the workflow before sending to production.
Also adding the ability to add asset objects to the database feature that was released would be amazingly cool as well!
This will be a very useful feature to have. Because "Export Issues" option limits the export results to 1000 row only. The alternative to this would be "Open in Excel" option. But when opted for that, the custom fields (from Assets) are not showing. The column shows as "No field found". See below example 
We are very interested in getting this option. To be able to report on ASSETS.
Please work on this enhancement. Assets are so useful but there are many rough elements which make it feel like an unfinished feature.
I hope this gets prioritised. We are using the workaround, but it is not good enough. The current workaround adds unnecessary clutter to Jira custom fields, field configuration, automation, etc..
Also looking for this to be fixed. It significantly limits our use of this add-on without including Asset data. The workaround of creating duplicate fields we then need to manage and keep in sync via automations is not feasible for us.
The lack of work on this issue is causing significant issues to our organization. We use asset fields for a number of objects and love the way it works in Assets... except for this issue. This issue is causing us to have to look at our process and in that exploration, look into other tools that could work better for us than the way Jira works for us now.
And yes, we are already using the workaround and it has significant challenges with fields that have a large number of changing objects and with the number of tickets we are pushing through the system... causing our automation numbers to be huge.
I cannot stress enough how much of an issue this is for us.
Oddly enough if you export using "my defaults", assuming the custom field is in your default list, the custom field exports the ID just fine BUT you can only get 1000 records at a time doing it that way. If it can work for 1000 records exporting FROM Jira, can you not simply mimic the code so that excel can PULL the same out of Jira? Please, I'm just asking for the ID, we can totally work with that.
In addition to the comment above regarding using more of your automation quota to put in the work around, I will also have to bulk edit 10,000+ records to be able to report on my teams efforts. Not being able to report, using a feature built for just that (surely everyone needs to report on their assets) seems like a fundamental flaw that should have a fairly easy fix.
Atlassian, you have a workaround in which you ask to us to use Automation rules ([Export Assets Object fields to Spreadsheets and Word | Jira | Atlassian Documentation|https://confluence.atlassian.com/jirakb/export-assets-object-fields-to-spreadsheets-and-word-1167741095.html]). Meaning we have to sacrifice some of the available automations to "fix" the bug after your recent changes to the usage of rules. You see what I mean?
+1