For Jira Cloud administrators

Which apps has nobody actually set up?

Someone installed a Marketplace app for a project in 2023. The project ended. Nobody uninstalled it. The subscription renews every year, quietly, forever. This finds the ones worth asking about before your next renewal — and tells you plainly where it cannot see.

Jira Cloud gives you no way to see which apps are actually being used. The request for it — ECO-470 — has been open more than four years with 383 votes, and the equivalent tool that exists for Data Center has no Cloud version. So admins audit by hand, or don't audit at all.

What it gives you

It reads the configuration surfaces that record app ownership and that Jira exposes to apps — custom fields and dashboard gadgets (workflow rules are read but not yet verified against a real app-provided rule) — and attributes each element back to its owner. Then it cross-references your billing list. Apps that appear nowhere are the ones worth questioning.

The first thing it tells you needs no input at all. An app registers the dashboard gadgets it offers whether or not anyone ever uses one. Comparing that against the gadgets actually placed on your dashboards gives you a finding in the first thirty seconds — and unlike "has no configuration", it does not wrongly accuse reporting apps, because offering is exactly what they do.

Example: Great Gadgets — 20 gadgets offered, none on a dashboard.

And where an app has actually been working, you get a date. Apps act through their own Jira account, so when one changes an issue, Jira records and timestamps it exactly as it would a person's edit. Reading that back gives hard evidence rather than inference: “this app last changed an issue on 12 March.” Anything caught working is excluded from every finding, so it can only ever shorten your shortlist — never lengthen it.

It cuts one way only. Seeing an app work proves it is in use; not seeing it proves nothing, because an app that only displays things never writes to an issue at all.

Illustrative figures. "None found" means no configuration footprint was detected — not that the app is unused. Jira exposes no last-viewed or last-run timestamp to an app, so this measures what has been set up, never what is being looked at.

Three steps, in this order

What it cannot see

This product asserts a negative — "nothing uses this" — and a wrong answer means someone cancels software their team depends on. So it is built to say "cannot judge" rather than guess:

• Reporting and panel apps are invisible to it. We installed a real, working reports app and it created no custom fields, gadgets or workflow rules — so this tool would list it as having no footprint. Anything whose value is what it renders, rather than what it writes into your configuration, cannot be detected this way. This is a limit of the method, not a bug we intend to fix.
• No footprint is therefore a shortlist, not a verdict. Confirm with your team, the vendor, or a 30-day unsubscribe test before cancelling anything.
• If any part of the scan fails, it withholds all cancellation advice rather than under-reporting and inventing savings.
• Forge apps are identified internally by installation ID, which billing exports don't contain. Those are listed as needing review, never as unused.
• It reads your configuration, plus issue history metadata — who changed an issue and when, which is how apps caught working are dated. No issue content is ever read: not summaries, not descriptions, not comments, not field values. Nothing is stored beyond the renewal costs you type in yourself, and nothing ever leaves Atlassian's infrastructure.

Get it

Free, permanently. One click — nothing to sign up for, no account to create. It installs by direct link while the Atlassian Marketplace listing is being prepared.