FactorantDocs / Jira checks
Jira checks
What one scan looks at, area by area. Red means it can break work or block you; amber means worth a look.
FieldsMost common
Custom fields with no use found, fields that share a name, fields made by apps, and fields with no context.
How it decides
A field counts as used when it is on a screen the app can read, named in a saved filter's search, or used by a board's filter, sub-query or estimation. Team-managed screens, automation, workflows, dashboards and request forms are not read. Each row says when a value last changed, where Jira keeps that. Open a field to see where it is used and the steps to take.
You can choose a date and press Plan removal: the app changes nothing in Jira, but lists your plans with an announcement ready to copy, and each space admin sees them on My space.
Schemes
Schemes in use, and how many serve one space only.
How it decides
Many one-space schemes make a site hard to change. This is shown for information, so you can plan to share schemes.
Permissions & security
Permission and issue security schemes used by one space only, schemes shared very widely, and spaces with no issue security scheme.
How it decides
A count of each, with the schemes named, so you can tidy them.
Screens
Screens in no live space's screen scheme, and screens with a tab holding more than 100 fields.
How it decides
A screen in no screen scheme can still be a workflow transition screen, so check workflows before you remove one. The Cleanup report gives the order.
Filters & boards
Filters that name a field that no longer exists, and boards whose filter is gone or private.
How it decides
Such a filter returns an error or nothing; such a board shows nothing to most people.
Access
Grants that open a lot up, such as Browse projects for all logged-in users.
How it decides
If a finding is on purpose, press Mark as intended; from the next scan it stops counting as a problem, and the mark is kept for a year. The list can be downloaded as a CSV.
LeaversCan break work
People with no Jira access who still lead a space or component, are a default assignee, own a filter or are named in a scheme.
How it decides
Those who can break work today come first. Each person has a page with what they hold, and there is a hand-over CSV. Names are looked up from Jira when you open the page, not stored.
Cleanup report
Workflows, schemes and screens with no known use, and what must wait until something else is removed first.
How it decides
No known use does not mean safe to remove. Check the items the app cannot see before you delete anything.
Jira limits
How close your site is to Atlassian's limits, such as fields per space or permission grants per permission.
How it decides
Limits are enforced: Jira refuses changes past them. Guardrails are advice: Jira does not refuse, but the site can slow down. Each shows Over, At the limit, Near (from 80%, our own threshold), OK, or Not checked with the reason. It is a quick check of its own, not part of the scan.