DEV Community

LLMGraph
LLMGraph

Posted on Originally published at katabarwalabs.dev

JSM Assets has no bulk export. Here is the AQL workaround and a one-click option

#atlassian #jira #devops #itsm

Sooner or later every Assets (formerly Insight) admin needs the whole CMDB out: an auditor wants the asset register, a migration needs a baseline, or someone sensible wants a backup before a big cleanup. Then you hit the gap: Jira Service Management Assets has no built-in bulk export of an object schema. The feature request has been open for years with hundreds of votes, and the accepted workaround is exporting object type by object type, by hand.

Why the native path hurts

  • The UI exports one object type at a time; a real schema has dozens
  • Attributes vary per type, so naive concatenation gives misaligned columns
  • Assets reads are gated behind schema roles, separate from Jira permissions, which surprises every script author on their first 403

The DIY approach: page the Assets REST API with AQL

  1. List schemas and object types via the Assets workspace REST API
  2. For each object type, page through objects with an AQL query (objectType = "..."), requesting attributes with each page
  3. Normalize per-type attribute columns before writing CSV, or emit JSON and defer the flattening
  4. Handle pagination limits, rate limits, and the schema-role grant for the account the script runs as

It works. It also becomes another script that has to live somewhere, keep an API token somewhere safer, and survive the next person asking for the same export six months later.

The packaged version

We productized this as Assets Export Manager for Jira Service Management (disclosure: I am the author). Pick a schema, pick CSV or JSON, and it exports every object with all attributes in one run. It is a Forge app: the export is generated on Atlassian's platform inside your tenant and streamed to your browser, so nothing leaves your instance. Read-only, and honest about limits: very large schemas are truncated with a clear flag rather than silently cut.

One setup note, stated upfront because it is the number one support question shape for any Assets integration: after install, grant the app read access on each schema's Roles tab. Assets gates reads there, not in Jira permissions. Then it just works.

Free for up to 10 users. If your export workflow needs something this does not cover, tell us and we will build it.

Top comments (0)