Fixed Asset Register for Jira (Sortable IT Assets & Licence Tracking)

Sort and filter your IT asset and licence register by any custom field, catch expiring licences before they lapse, and stop duplicate rows on re-import — all inside Jira.

• Marketplace listing: Fixed Asset Register for Jira (Sortable IT Assets & Licence Tracking)
• Current version: 4.0.0 (published 2026-08-23)
• Works with: Jira Cloud
• Pricing: £7.90 per month, flat, billed by Atlassian through the Marketplace
• Support: layercell.com/support
• Privacy notice: layercell.com/privacy

What it does

The app adds a register to your Jira site: two views — Assets and Licences — each holding types you define, rendered as a sortable, filterable grid with licence-expiry warnings and CSV import that updates instead of duplicating. It is aimed at small-business admins who keep the company's assets and licences in Jira and want them findable and expiry-aware without exporting to a spreadsheet.

Install

1. Click Get app on the Marketplace listing.
2. Approve the permissions. The app requests exactly two scopes: storage:app (its own storage) and report:personal-data. It reads nothing from Jira issues and writes nothing to them.
3. Open Apps → Fixed Asset Register for Jira from Jira's administration. The page is admin-facing; decide internally who maintains the register.

Getting started

1. Pick a view — Assets or Licences — at the top of the page.
2. Define a type (for example "Laptops" under Assets). Every type starts with built-in fields: assets have Name; licences have Name, Expiry (date) and Seats (number).
3. Add custom fields to a type — text, number, date, or select. Any field of one of these types can be made sortable; declaring it provisions a matching index before the field accepts data, so sorting stays fast.
4. Add rows, one per asset or licence.

Using the grid

• Sort by clicking a column header on any declared-indexed field; visible rows update without a full page reload.
• Filter with the search box (matches across fields), then page through results 50 rows at a time.
• Expiry warning: a licence whose expiry date falls within its type's warning window shows an indicator in the grid and in the licence's detail view. The window is configured per type and defaults to 30 days.
• Everything is operable by keyboard alone; every control and status message is exposed to screen readers, and focus is always visible.

Importing from CSV

Import CSV accepts a pasted or uploaded file (up to 5,000 rows or 5 MB).

1. Configure the matching key for the type — which column(s) identify a row.
2. Import. Rows whose matching key already exists are updated, not duplicated; the status line reports "Imported N, updated M".

Re-running an import against the same inventory is therefore safe: you get one row per asset, not a growing list.

Exporting and erasing

• Export downloads all of your site's register data as CSV.
• Delete account data removes everything the app holds for your site.
• Admins can also look up and erase data about a named person by identifier.
• Uninstalling runs cleanup immediately; anything remaining is removed within 30 days.

Data handling

• Every storage query is scoped to your Jira site's cloudId, enforced at the data layer. No URL, export, or shared cache surfaces another tenant's rows.
• The app stores only what you enter or import: asset and licence records, their type/field definitions, and configuration (matching key, warning window). Imported assignee names or emails are adult staff PII held solely to label who an asset belongs to.
• No health, biometric, under-18, or payment-card data, ever.

Limits and non-goals

• Registers larger than 5,000 rows are not supported; neither is import chunking for inventories beyond a single invocation.
• Sorting and filtering work on declared-indexed fields only.
• Imports are manual CSV only — there are no connectors into Intune, Jamf, or Active Directory.
• Ingest is one-way: the app never syncs back to any external source.

Pricing and billing

£7.90 per month flat, billed monthly by Atlassian through your Atlassian billing account. There is no per-user charge and no usage metering.

Layercell Ltd is a company registered in England and Wales, company number 17363808. Registered office: 111 Upper Grosvenor Road, Royal Tunbridge Wells, TN1 2EA.