Stop paying for the junk in Jira Assets
The same laptop from three different imports. Servers switched off in 2023. It all counts towards your Assets object allowance, and from 3 December, monthly plans pay $0.02 a month for every object over it.
We're building a Forge app that finds the duplicates and dead records, retires them without losing ticket history, and keeps the count where you want it.
What a scan shows
42,318objects in Assets
$726.36a month for the 36,318 over the allowance
- In use
- 28,735
- Updated, linked or referenced recently
- Stale
- 7,962
- No changes or ticket links in 12 months
- Duplicates
- 3,407
- Same serial, MAC or hostname as another
- Orphaned
- 2,214
- Nothing references them, no ticket links
Assets is billed by the object now
Every paid Jira, Teamwork Collection and Service Collection plan comes with an Assets allowance, and allowances from different subscriptions add up across your organisation.
Over the allowance, each object costs $0.02 a month. Annual plans already pay for extra objects. Monthly plans, and anyone who started on Assets after 1 September 2026, start paying on 3 December 2026.
The count is a snapshot of what's in your schemas, so there's no trick to it: the bill only comes down when the number of objects does. An organisation on Service Collection Standard and Jira (6,000 included) holding 40,000 objects pays $680 a month. On Premium and Jira (51,000 included), 200,000 objects cost $2,980.
| Plan | Objects included |
|---|---|
| Jira Standard, Premium or Enterprise | 1,000 |
| Teamwork Collection | 5,000 |
| Service Collection or Jira Service Management Standard | 5,000 |
| Service Collection or Jira Service Management Premium | 50,000 |
| Service Collection or Jira Service Management Enterprise | 500,000 |
From Atlassian's licensing page, checked 17 October 2026.
What the app does
It works on top of whatever already feeds Assets, whether that's Assets Discovery, CSV and LDAP imports, an importer app or people typing things in.
Shows you what's in there
A daily, read-only scan of every object, counted by schema and object type, with everything stale, duplicated, orphaned or missing key attributes picked out. It also projects your month-end count against the allowance.
Merges duplicates
Matches records across object types and imports on serial number, device IDs, MAC address and hostname. It suggests which record to keep, moves references and ticket links onto it, then retires the copies.
Retires objects without losing history
Stale objects go in batches that someone signs off. Each one is written to a Jira work item with its attributes and ticket links, then deleted so it stops counting. If you need it back, you restore it from that work item.
Gives every record an owner
Owners are assigned by rule: by object type, location, team or whatever fits your schema. Review campaigns then ask each owner to confirm, fix or retire what's theirs, so the admin isn't chasing everyone.
Keeps the bill in view
Forecasts extra usage at $0.02 an object, shows what each clean-up saved and warns you before you cross a threshold you've set.
Ground rules
- Your data stays in Atlassian. It's a Forge app with no outside connectors, so nothing from Assets is sent anywhere else.
- It starts read-only. The scanner changes nothing, so you can see the state of your schemas before deciding what to touch.
- Nothing is deleted without sign-off. Someone approves every batch, and every object gets an archive copy first.
Who it's for
Jira and JSM admins, and the asset or configuration managers who look after Assets day to day. It's built for organisations of roughly 100 to 5,000 people with 10,000 or more objects and more than one thing feeding Assets.
And for Atlassian Solution Partners who run Assets for clients. Join with your work email and we'll be in touch about partner access.
What it isn't
- Another importer. Version 1 doesn't connect to Microsoft or anything else outside Atlassian. It looks after what your existing feeds put into Assets.
- A copy of Data Manager. It doesn't build records from raw sources. It works on the objects already in your schemas.
- An ITAM suite or a backup tool. No contracts, licences or depreciation, and Atlassian's own backup already covers Assets.
Questions
When can we try it?
We're aiming for the Atlassian Marketplace in early 2027. People on the waitlist get the read-only scanner before then.
Does any of our data leave Atlassian?
No. The app runs on Forge, Atlassian's own app platform, and the first version has no outside connectors. Your Assets data isn't sent anywhere else.
Will it delete anything on its own?
No. It suggests what to retire and a person approves each batch. Every object is copied to a Jira work item, with its ticket links, before it's deleted, and you can restore it from there.
We already import from several tools. Does this replace them?
No. Keep your importers. The app deals with what they leave behind: overlaps between feeds, objects nobody updates and records nobody owns.
We have Data Manager. Do we need this?
Maybe not. Data Manager reconciles source data before it reaches Assets, and it comes with Service Collection Premium and Enterprise. We're building mainly for teams without it, although owner reviews, safe retirement and the bill forecast are useful either way.
Does it work on Data Center?
No. It's built on Forge, which only runs on Atlassian Cloud.
What will it cost?
It'll be a paid app on the Atlassian Marketplace, priced per user like most Marketplace apps. We'll publish prices before launch, and the waitlist will see them first.
Can we get a scan before launch?
We're running a small number of early assessments for organisations that need one now. Join the waitlist and reply to our first email.
Is this made by Atlassian?
No. We're an independent team building on Atlassian's platform, and the app isn't affiliated with or endorsed by Atlassian.
Get the scanner first
The waitlist gets the read-only scanner before the Marketplace launch. It runs on your site and changes nothing.