Integrate Jira Service Management with 3rd party CMDB and Asset Management

Question

Hello,

For our use case, Jira Assets is inadequate as a solution for an asset management system and CMDB in many respects. I don't want to go into the specific reasons in detail in this post, as they are very company-specific.

However, I am happy to answer any questions from interested parties 😀

Instead, I'd rather talk to other Atlassian administrators and developers about whether and what experiences you have had with the integration of third-party asset management systems and CMDBs.

In your opinion, are there any solutions on the market that stand out and are particularly well suited?

I look forward to your suggestions or recommendations and would also be happy to hear from you directly, e.g., via LinkedIn.

Best regards,

Alex

Alexander Ziegltrum · Answer

@Matteo Vecchiato @Matteo Vecchiato

thank you for picking up this topic. Since Jira Assets has too many downsides and weaknesses with our certain business case, it doesn't seem to make sense, to integrate a 3rd party tool with Assets and that again with Jira.

Matteo Vecchiato · Answer

I @Aron Gombas _Midori_ ,

Thank you for your post.

My recommend to integrate/synchronize the external CMDB with Assets, and not directly with Jira.

You could have your own CMDB, and "only" have a representation of data in Jira Assets.

Having this, you can use all the features.

Moreover, now with Data Manager is easier to integrate assets with external tools

Aron Gombas _Midori_ · Answer

A few years ago, there was a general custom field type for assets, and there were several apps that integrated third party CMDB systems by managing the values in this field. Insight (which became Jira Assets later) was only one of the options, even if the most popular one.

I noticed some time ago that this custom field type ago disappeared, at least it did on our site... I don't know about the apps that relied on it.

I know that it is not a real answer to your question, but seems that the platform now has a strong "preference" (khm) towards its own solution.