A migration lead wants the current state, an auditor wants evidence, or you want a backup before a big change. You go looking for the export-this-schema button in Jira Service Management Assets and there is no one-click export of a whole object schema.
It is one of the longest-standing asks on the JSM tracker: JSDCLOUD-9967 ("Ability to export Assets data from Object Schema") has over 580 votes and is still open. You can build the export yourself, but it is a real script you then own: find the workspace id, AQL-page every object, resolve each attribute id to its name and flatten to display values, honor Assets rate limits (429s and Retry-After), and escape CSV against formula injection.
Disclosure: I work for Katabarwa Labs, and we build an app for exactly this, so treat it as one option among whatever you evaluate.
Assets Export Manager does that whole flow as a single action. You pick an Assets object schema, choose CSV (one row per object, audit-ready) or JSON (full-fidelity and re-import-friendly), and it AQL-pages every object, flattens each object's attributes to display values, and streams the finished file to your browser. Each export carries a manifest: schema, object count, per-object-type breakdown, timestamp, and a truncation flag, so you know exactly what you got. It runs entirely on Atlassian Forge inside your own tenant, so nothing leaves your instance, and it reads only the schemas you grant it on each schema's Roles tab.
Listing, if it helps: Assets Export Manager for Jira Service Management. If your export workflow needs a shape this does not cover, tell us and we will build it.
Abaho Katabarwa _Katabarwa Labs_
0 comments