Jira Assets (CMDB) and JSM: Forge sync patterns that survive imports

Jira Assets (CMDB) plus JSM is powerful—and unforgiving. Forge apps that “just POST objects” hit import limits, permission gaps, and opaque errors like ingest-finished states. Design sync as an import pipeline, not a chatty loop.

Patterns that work

• Batch via Assets import APIs; mark isComplete once.
• Map external ids → Assets object keys for idempotent upserts.
• Use AQL in read paths; cache schema lookups.
• Separate “suggest Assets on issue” (UI/Rovo) from “nightly CMDB sync” (import).

Permission reality

App access ≠ human Assets schema permission. Test as app and as agent roles. Rovo/Assets skill mismatches produce 401s that look like Forge bugs—verify skills and schema access first.

JSM glue

Link request types to Assets fields carefully; validate objects exist before transition. Portal users should never see internal CMDB identifiers unless product requires it.

Need this built? HostHob ships production integrations and Marketplace-ready apps from Rotterdam. See our services or Build an Assets + JSM sync.