Documentation
License Asset Tracker for Jira (CSV Import & Expiry Tracking)
Jira admins at medium-large orgs cannot track IT asset licenses at scale: they can't sort or filter asset data, they have no discovery or integrations, and CSV import/export is deceptively hard. The incumbent's own Marketplace listing has 7 complaints, so the job remains undone.
Overview
Jira admins at medium-large orgs cannot track IT asset licenses at scale: they can't sort or filter asset data, they have no discovery or integrations, and CSV import/export is deceptively hard. The incumbent's own Marketplace listing has 7 complaints, so the job remains undone.
Key Features
- A Jira admin can create an asset with custom fields, edit it, and delete it; after each save the list updates without a page reload.
- The asset list can be sorted by any displayed column and filtered by any custom field value using client-side data.
- CSV import maps columns, validates each row, imports valid rows, rejects invalid rows, and displays counts of imported and failed rows.
- When a license expiry date has passed, the app creates a Jira issue in the configured project and that issue is visible in the project.
- An admin can export the installing tenant's asset data to CSV and can erase that data; the exported file contains only that tenant's assets.
- A user authenticated to tenant A cannot read tenant B's assets by direct URL, by API call, by CSV export, or via a shared cache; all data access is scoped to the installing tenant's Forge storage.
Getting Started
Install the app into your Jira instance from the Atlassian Marketplace.
Stuck
Ask a person.
If this guide does not answer your question, email us and a human answers. Name the product, what you were doing, and what happened instead. That is genuinely all we need to start.