Uploaded image for project: 'Atlassian Product Integrations'
  1. Atlassian Product Integrations
  2. API-491

Add the ability to export Assets objects field using Excel and Google Sheets

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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.

            [API-491] Add the ability to export Assets objects field using Excel and Google Sheets

            +1 

            Adrián Cano added a comment - +1 

            please make this work. I dont understand why this wouldn't be a default feature. 

            Jaime Ortiz added a comment - 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..

            Hayden Mccarry added a comment - Very interested in making this a feature. Assets should be exportable as normal during reports..

            I would love to have this option!!

            Katarzyna Sutor added a comment - I would love to have this option!!

            +1 Please

            Claudio de Lima Sales added a comment - +1 Please

            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!

            Trevor Leadley added a comment - 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

            Rathnayake, Malshani added a comment - 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. 

            Katia Cypers added a comment - We are very interested in getting this option.  To be able to report on ASSETS. 

            r_cull added a comment -

            Please work on this enhancement. Assets are so useful but there are many rough elements which make it feel like an unfinished feature. 

            r_cull added a comment - Please work on this enhancement. Assets are so useful but there are many rough elements which make it feel like an unfinished feature. 

            Milad S. added a comment -

            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..

            Milad S. added a comment - 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..

              Unassigned Unassigned
              ccd19600178e Anchal Chopra
              Votes:
              202 Vote for this issue
              Watchers:
              89 Start watching this issue

                Created:
                Updated: