Jira Cloud has introduced optimisation tools to help enterprise admins tackle configuration sprawl — unused custom fields, work types, screens, and schemes that accumulate over time and degrade performance. The system uses a pre-computation framework that asynchronously scans Jira data per space, produces usage reports, and surfaces bulk remediation actions (like dissociating unused fields or splitting schemes). Key engineering decisions include prioritised refresh only for spaces nearing limits (~70% utilisation), polymorphic 'usage' tables instead of per-entity tables to avoid millions of database objects in a multi-tenant architecture, and full audit logs with assisted rollback for safety. Since launch, admins have removed tens of millions of unused fields and work types, with some customers cleaning up hundreds of thousands in a single day — a process that previously took weeks.
Table of contents
High-level overviewHigh level architectureOptimisation tools and site optimiser view in JiraPre-computation frameworkChallenges & SolutionsImpactSort: