Jira Software and Asset Discovery

[Michelle Kirk]

Hi, we are now looking at the best option to discover Assets last date on the network,  Software installed, by user, by device, and last utilised. 

I have looked at the Atlassian Marketplace and can see the following potential options. 

Option 1 - Atlassian Discovery appears to discover what we require, but doesn't show the available dashboard types or provide precise details about the discovery tool's capabilities for Software.

Option 2 - The other option is AssetIT, which appears to deliver what we are looking for. 

Software installed by User, by device, last used Assets last on the network
That produces good dashboards.

Has anyone able to provide any feedback on which option would be beneficial ?

[Jorge Cammarota · Accepted solution]

Hi Michelle, great question these two options address similar problems, but with very different approaches.

A few points to help with the choice (and also to clarify my doubts about your scenario):

Atlassian Assets Discovery (formerly Insight Discovery)

It is the "native" scanner for the Assets module in Jira Service Management.

It discovers devices on the network, collects hardware and installed software data per host, and can automatically update the CMDB (Assets).

The focus is more on technical discovery and CMDB integration than on ready-made dashboards. Dashboards are usually built on top of Assets objects (or via Atlassian Analytics / external BI).

Questions for you:

Do you already use Jira Service Management + Assets/CMDB, or is it currently just Jira Software?

Do you need this data to feed an asset/CMDB repository within Jira, or just reports/dashboards?

AssetIT

From what you mentioned and from what I saw in the Marketplace listing, it seems to deliver directly what you are looking for:

software installed per user, per device, and last seen on the network / last usage;
ready-made dashboards focused on asset management and software inventory.

In general, these third-party apps already come with operational panels ready to use, which significantly reduces initial effort if the main goal is visibility/reporting, rather than a complex CMDB.

How I would compare them, in summary:

If the main goal is:

to have a CMDB integrated with Jira, feed relationships (service → host → software → incidents), use automations on top of Assets items → Assets Discovery + Assets tends to make more sense.

If the main goal is:

to quickly have inventory and dashboards of software per user/device, with good visualization, without building much of a data model in Assets → AssetIT will likely be more straightforward and faster to put into production.

I hope I’ve answered your question and contributed in some way.

[Michelle Kirk]

Hi thank you or your reply, to respond to your questions 

Questions for you:

Do you already use Jira Service Management + Assets/CMDB, or is it currently just Jira Software?  - We have just built Jira SM and the Asset function (gone live today), we currently do not have Software built into Jira (but the goal is to)

Do you need this data to feed an asset/CMDB repository within Jira, or just reports/dashboards?  - Ideally yes I want the software visible within the Asset, but then be able to report separately on under utilised software. 

Based on what you have kindly provided it will be to have a CMDB integrated with Jira, feed relationships (service → host → software → incidents), use automations on top of Assets items → Assets Discovery + Assets

One QQ do we need to have built the software element within Jira before we go down the discovery route ?