Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Insight CMDB child object type mappings failing to import sporadically


I have an object type: Resource Server, and it has several child object types - such as Agent, SQL.  The Resource Server parent has 10 attributes that are inherited by its child object types.  The Resource Server object type itself is ABSTRACT.

I am imported data into these object types using JSON. I created an import configuration that maps to object type Resource Server and it has child object type mappings for both Agent and SQL.    

I am unable to import consistently. The import will often complete the indicate it saw 0 entries in the external source (screenshot to be attached).  Occasionally, I will disable all but 1 or 2 child object type mappings and the import works as expected.  The json file is uploaded to the server, so it is not that it cannot be read/reached.

Any ideas on what would cause this inconsistent behavior?

Please note: the examples in the documentation are for CSV imports and Selector is used to differentiate child object types.  With JSON, Selector is not available, so I use "Filter data source by IQL".

1 answer

I just face the same issue on Jira 8.21.1 and Insight 9.1.3.

And I'm unable to find any config pattern that cause this bug....

Did you find anything?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events