Unitlane logo UnitlaneJira cleanup tools
Products

Choose the right Unitlane Jira app.

Start with the decision your team needs to make: reduce wasted seats, change a Jira group without blind spots, or preserve evidence from a JSM request.

Find wasted seatsScan groups before cleanupReview evidence packs
Three appsPaid via AtlassianPreview-firstClear limits
Compare by jobThree apps, three different admin decisions.

Pick the lane by the record, scan, or handoff your team needs next.

License and renewal cleanupLicense Guard

Find wasted seats, review billable paths, and preview cleanup before changing access.
Jira group preflightGroup Cleanup Radar

Check group references, cleanup candidates, blockers, and coverage gaps before group changes.
JSM evidence handoffRequest Evidence Control for JSM

Show reviewed evidence, missing-source caveats, accepted warnings, and the export record.
Product comparison

At-a-glance comparison

Each app has a different job, output, and boundary. That makes the right next click faster for evaluators.

License Guard

Cost savings
Use whenRenewal cost, wasted seats, or billable-access review is the pressure.
OutputSavings scan, estimated impact, billable paths, cleanup preview, and export.
BoundaryEstimates and preview-first review, not savings guarantee or account deletion.
Open License GuardRead docs

Group Cleanup Radar

Jira group preflight
Use whenA Jira group may be deleted, renamed, replaced, or cleaned up.
OutputAll-groups radar, group preflight, findings, and coverage matrix.
BoundaryRead-only review, not delete or rename approval.
Open Group Cleanup RadarRead docs

Request Evidence Control for JSM

JSM evidence handoff
Use whenA JSM request needs a durable handoff after review or closure.
OutputReceipt, manifest, source status, accepted warning, and preserved caveats.
BoundaryShows missing evidence instead of inventing historical proof.
Open Request Evidence Control for JSMRead docs
Comparison matrix

Compare the apps

The important difference is not the UI theme. It is the job, the user, and the review artifact each app produces.

Question
License Guard
Group Cleanup Radar
Request Evidence Control for JSM
Primary job
Find wasted Jira seats and cost-saving opportunities before renewal.
Find group dependency risk before delete, rename, or cleanup work.
Turn a JSM request review into an evidence pack with caveats preserved.
Main user
Jira admins and finance owners reviewing renewal spend.
Jira admins checking group references and coverage gaps.
JSM admins, access reviewers, and audit handoff owners.
Output
Savings scan, estimated impact, billable paths, and export.
All-groups radar, preflight details, findings, and coverage matrix.
Receipt, manifest, source status, accepted warning, and preserved limitations.
Not for
Deleting accounts or guaranteeing billing savings.
Automatically deleting, renaming, or modifying Jira groups.
Inventing proof when historical source evidence is unavailable.
Decision helper

Start here if

Use the first true sentence. The product route should feel obvious before anyone reads a long feature list.

Savings firstRenewal cost is the problem and wasted seats need review.

Start with License Guard.

 Risk firstA Jira group may be deleted, renamed, replaced, or cleaned up.

Start with Group Cleanup Radar for Jira.

 Proof firstA JSM request needs a durable record of what was reviewed.

Start with Request Evidence Control for JSM.
FAQ

Questions before choosing

Which product should I start with?

Use License Guard for wasted Jira seats and renewal cleanup. Use Group Cleanup Radar before deleting, renaming, or cleaning up Jira groups.

When should I use Request Evidence Control for JSM?

Use it when a JSM request needs an evidence handoff that shows what was reviewed, what was missing, and what was accepted.

Do these products make blind changes?

No. License Guard is preview-first by default, Group Cleanup Radar is read-only by design, and Request Evidence Control for JSM preserves limitations instead of turning missing evidence into proof.