Creating Asset Incident Trend Reports

[ian_silver]

I'm looking for a way to create a report for my infrastructure team that shows all assets that have had 3 or more incidents linked to them in the past 6 months.

We currently pull assets from Device42 via their direct integration to JSM Premium. 

We are also exploring their integration to Jira Assets.

I can generate a list of all incidents from the past 6 months with the linked assets displayed, using something like this:

project = ITSM AND issuetype = "[System] Incident" AND created >= -26w AND "Linked assets[Assets]" != ""

However, this does not allow me to group by assets, nor even sort by assets, and if I export to Excel, I currently lose the human-friendly value of the assets listed.

Does anyone have experience working with asset data in Jira Assets pulled from a 3rd party source?

Once we have the Device42 to Jira Assets integration in place, will Jira Assets support the export and grouping I need to do?

[Joseph Chung Yin]

@ian_silver -

Once you have migrated or integrated your Device42 and Jira Assets, what you will need is to create new custom JSM/Jira issue fields (sourced from Assets schema) and apply those fields to your JSM project issues.  After you populated those fields within your JSM issues, then your JQL will work properly.

I can only assumed that your existing custom field "Linked assets(Assets)" is a text format field?  Thus, you have difficulty in grouping your data.

Here is the reference link on custom field setup sourcing from Assets schema - https://support.atlassian.com/jira-service-management-cloud/docs/set-up-the-assets-object-field/

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[ian_silver]

Thanks for the response Joseph.  We are still working through some issues with the integration.

We have been using an earlier integration that connects directly to JSM from Device42.

The Linked Assets field is not a text custom field that we created; it is part of this integration and populated dynamically via an API call.  The values DO appear in search results, but cannot be manipulated (e.g. sorted) or exported.

This is why we are exploring the newer integration to Jira Assets, hoping that we will be able to transform these into static values that we can manipulate and export.

Thanks also for the pointer on custom field setup from Assets.