Provide a unified admin view to identify all schemes not associated with any project (orphaned scheme report)

XMLWordPrintable

      Problem Definition:

      As Jira Cloud sites grow, schemes of all types (workflow, permission, notification, issue type, screen, field configuration, issue security) accumulate and become orphaned when projects are deleted or reconfigured. There is currently no single admin view that surfaces all orphaned schemes across all scheme types.

      Admins must manually navigate to each scheme type's configuration page and visually inspect the "Projects" column to find unlinked schemes — a process that is tedious and error-prone at scale, especially for sites with hundreds of schemes.

      Site Optimizer addresses some cleanup scenarios but does not provide a comprehensive, filterable list of all orphaned schemes grouped by type.

      Suggested Solution:

      Provide a dedicated admin page (or enhance Site Optimizer) with:

      1. A unified list of all schemes across all types (workflow, permission, notification, issue type, issue type screen, screen, field configuration, issue security, priority) that are not associated with any active project.
      1. Filtering by scheme type, creation date, and last-modified date.
      1. Bulk selection and bulk delete capability for confirmed orphans.
      1. A "dry-run" or export mode (CSV) so admins can review before taking action.
      1. Clear indication if a scheme is the system default (to prevent accidental deletion).

      Why this is important:

      • Enterprise sites can accumulate thousands of orphaned schemes after project migrations, archival, or deletion.
      • Manual identification doesn't scale and introduces human error.
      • Orphaned schemes clutter admin UIs (e.g., scheme pickers show stale options), increase cognitive load, and complicate governance audits.
      • This would reduce the need for third-party Marketplace apps or custom REST API scripts to perform basic configuration hygiene.

      Workaround:

      • Manually inspect each scheme type's admin page for the "Projects" column.
      • Use the REST API to iterate projects and build a scheme→project map, then identify unmapped schemes (requires scripting knowledge).
      • Use Marketplace apps such as "Optimizer for Jira" or "Admin Toolbox for Jira."

              Assignee:
              Unassigned
              Reporter:
              Joao Vasconcelos
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: