Instance Auditor for Jira - User Guide
Effective Date: March 23, 2026
Quick Start (≈3 minutes)
Command Center: Check red or amber indicators.
Inactives: Start with Fields or Screens.
Duplicates: Resolve the worst offenders first.
On This Page
- Command Center
- Duplicates
- Inactives
- Risks and Drifts
- Spaces
- Space Attributes
- Work Items
- Work Item Attributes
- Workflows
- Fields
- Screens
- Schemes
- Boards, Dashboards and Filters
- Groups and Users
🧭 Command Center
Command Center overview
Audience: Jira Admins, Governance Leaders
Why this matters: This is your single pane of glass for instance health--find risks fast and decide where to act first.
Scope
- Governance
- System Summary
- Configuration
How to Use
- Review Instance Score, Risk Signals, and Maturity Score.
- Scan for spikes (e.g., inactive items, duplicates).
- Click into the area with the biggest signal (Fields, Workflows, Screens, etc.).
- Use Refresh after making changes in Jira.
- Set your own KPI lower and upper thresholds.
Benefits
- Faster triage and time‑to‑action.
- Identify risks and cleanup opportunities, leading to an optimized and healthy instance.
- Visibility into risk and cost for leadership.
- Turns raw configuration into a prioritized to-do list.
- Tune lower and upper limits to your desired KPIs thresholds.
🧬 Duplicates
Duplicates overview
Audience: Jira Admins, Stewards
Why this matters: Duplicate configs create noise, increase maintenance cost, and confuse users/reports.
Scope
- Work Types
- Work Type Schemes
- Workflows
- Workflow Schemes
- Fields
- Screen Schemes
- Priority Schemes
- Filters
How to Use
- Group by name or type to spot likely duplicates.
- Decide on the authoritative item; rename or retire others in Jira.
Benefits
- Cleaner reporting and less user confusion.
- Lower run cost via reduced clutter.
- Foundation for analytics and auditability.
🧹 Inactives
Inactives overview
Audience: Jira Admins
Why this matters: Pruning inactives reduces risk and improves performance and user experience.
Scope
- Inactive Work Types
- Inactive Work Type Schemes
- Inactive Workflows
- Inactive Fields
- Inactive Screens
- Inactive Screen Schemes
- Inactive Work Type Screen Schemes
- Inactive Priority Schemes
- Inactive Notification Schemes
- Inactive Workflow Schemes
How to Use
- Start where counts are highest (often Fields or Screens).
- Open detail rows to see where items are used.
- Decommision in Jira; then Refresh here.
Benefits
- Smaller footprint and better performance.
- Governance and compliance benefits.
- Improved end-user experience.
⚠️ Risks and Drifts
Risks and Drifts overview
Audience: Jira Admins, Governance Leaders
Why this matters: Surface two fast movers for security and standardization: public exposure in permission schemes and workflow designs that have drifted into single‑use islands.
Scope
- Permission Scheme Security Risks
- Workflow Drift
How to Use
- Open Permision Scheme Security Risks → sort by Risky Grants or Space. Expand rows to see which permissions are public and which spaces use them; open the admin link to tighten or remove risky grants; retire schemes that are unused (✅).
- Open Workflow Drift → review workflows tied to schemes used by a single Active space. Expand detail to see scheme/space references and statuses; standardize or merge where appropriate; plan safe migrations.
- After applying changes in Jira, click Refresh to re‑evaluate the signals.
Benefits
- Lower data exposure risk by eliminating public anonymous access paths.
- Fewer one-off configurations; stronger reuse and simpler governance.
- Clear candidates for consolidation and decommissioning (schemes, workflows).
📁 Spaces (Projects)
Spaces overview
Audience: Portfolio Owners, Jira Admins
Why this matters: Clear lifecycle and ownership reduces sprawl, risk , and accidental data exposure.
Scope
- Active Spaces
- Archived Spaces
- Spaces in Trash
How to Use
- Validate Space Lead and management type.
- Confirm archive and trash dates before permanently deleting.
- Prioritize large or private spaces for review.
Benefits
- Portfolio hygiene and lifecycle clarity.
- Risk reduction via visibility into privacy and simplified flags.
🏷️ Space Attributes
Space Attributes overview
Audience: Portfolio Owners, Jira Admins
Why this matters: Standardized categories, roles, and versions enable consistent reporting and releases.
Scope
- Space Categories
- Space Roles
- Versions
How to Use
- Normalize categories for portfolio reporting.
- Review role actors and remove unused roles.
- Prune stale versions.
Benefits
- Predictable operating model.
- Release hygiene and reporting clarity.
🧩 Work Items
Work Items overview
Audience: Jira Admins, Governance Leaders
Why this matters: Right-sizing the catalog and reusing schemes cuts complexity and risk.
Scope
- Work Types
- Work Type Schemes
- Work Item Security Schemes
How to Use
- Right-size your catalog and reuse schemes.
- Validate security levels and memberships.
Benefits
- Fewer variants and stronger governance.
- Role-based visibility for compliance.
⚙️ Work Item Attributes
Work Item Attributes overview
Audience: Jira Admins
Why this matters: Consistent attributes improve user experience and analytics across teams.
Scope
- Resolutions
- Priorities
- Priority Schemes
- Work Item Linking
- Versions
- Labels
How to Use
- Keep lists concise; verify defaults.
- Ensure priority schemes are consistent.
- Standardize link semantics; prune stale versions and labels.
Benefits
- Consistent semantics accelerate delivery.
- Ensure priority schemes are consistent.
🔁 Workflows
Workflows overview
Audience: Jira Admins, Governance Leaders
Why this matters: Healthy workflows reduce cycle time and change risk.
Scope
- Active Workflows
- Workflow Schemes
- Statuses
How to Use
- Target stale designs; align scopes.
- Consolidate schemes; validate status names/categories.
Benefits
- Reduced cycle time and change risk.
- Lower maintenance overhead.
🗂️ Fields
Fields overview
Audience: Jira Admins
Why this matters: Fields are a top driver of clutter, confusion, and performance cost if unmanaged.
Scope
- Fields
- Fields in Trash Bin
- Field Configurations
- Field Configuration Schemes
How to Use
- Sort by last used or # screens to find consolidation targets.
- Use trash dates to decide on recovery vs deletion.
- Ensure configurations match intake patterns.
Benefits
- Lean forms and trustworthy data..
- Faster creation and search.
🖼️ Screens
Screens overview
Audience: Jira Admins
Why this matters: Screen consistency improves UX and reduces maintenance effort.
Scope
- Screens
- Screen Schemes
- Work Type Screen Schemes
How to Use
- Identify reusable standards and safe deprecations.
- Unify create/edit/view mappings where possible.
- Decommision unused schemes.
Benefits
- Better UX consistency.
- Fewer change points when policy evolves.
🛡️ Schemes
Schemes overview
Audience: Jira Admins, Governance Leaders
Why this matters: Well-governed schemes enable audit readiness and least-privilege at scale.
Scope
- Notification Schemes
- Permission Schemes
How to Use
- Remove unlinked notification schemes.
- Standardize permission schemes and minimize exceptions.
Benefits
- Audit readiness and least-privilege at scale.
📊 Boards, Dashboards and Filters
Boards, Dashboards, and Filters overview
Audience: Jira Admins, Stewards
Why this matters: Ownership and sharing posture impact visibility, security and change management.
Scope
- Boards
- Dashboards
- Filters
How to Use
- Fix orphaned or mis-owned boards.
- Audit dashboard/filter sharing and subscriptions; adjust ownership as needed.
Benefits
- Controlled visibility with high ROI.
- Better change management informed by favorites and subscriptions.
👥 Groups and Users
Groups and Users overview
Audience: Jira Admins, Governance Leaders
Why this matters: Clear group hygiene and admin oversight enable least-privilege and continuity.
Scope
- Groups
- Active Jira Users
- Jira App Users
- Former Users
How to Use
- Surface admin-like groups and memberships.
- Validate app/bot accounts.
- Plan reassignment from former users.
Benefits
- Least‑privilege and continuity.
- Reduced breakage in dashboards and filters.