How to Audit and Reduce Custom Fields in Jira Before the 700-Field Limit Hits

[#1]

Many Jira admins only discover configuration sprawl when something breaks—or when a platform limit appears.

With Atlassian introducing a 700-field limit per field configuration in Jira Cloud, many large instances are suddenly much closer to that limit than expected.

Over time, most Jira instances accumulate hundreds of custom fields, duplicated project roles, and stale versions scattered across projects.

However, Atlassian is introducing new guardrails in Jira Cloud that cap the number of fields allowed in a field configuration to 700. That “tomorrow problem” has now become a hard operational constraint.

If you are preparing for a Cloud migration or managing a large-scale Jira instance, understanding your configuration footprint is no longer optional—it is essential for maintaining a healthy and manageable system.

---

The Problem: The Manual Audit Trap

Jira does allow administrators to inspect configuration relationships, but doing so manually quickly becomes impractical.

To safely delete a single custom field, an administrator typically needs to check:

• Every Screen and Screen Scheme

• Every Workflow transition where the field might appear

• Every Issue Type Screen Scheme

• Every Workflow Scheme

• Every Project configuration

For a Jira instance with hundreds of fields and dozens or even hundreds of projects, performing this analysis manually is extremely time-consuming.

This is the manual audit trap many administrators encounter when trying to clean up their configuration.

---

Config Insights for Jira: Built for the New Field Guardrails

Config Insights for Jira is a Forge-native bundle designed to help Jira administrators understand and manage configuration usage at scale.

It combines three specialized tools:

• Fields Usage for Jira

• Roles Usage for Jira

• Versions Usage for Jira

Together they provide a structured overview of how configuration elements are used across the entire Jira instance, helping administrators identify redundancies and make safe cleanup decisions.

---

1. Fields Usage: Solve Custom Field Sprawl

The most urgent challenge for many Jira administrators today is custom field sprawl.

Fields Usage for Jira provides a comprehensive map of where each field is used across the instance, including relationships with:

• Screens

• Screen Schemes

• Issue Type Screen Schemes

• Workflow transition screens

• Workflow Schemes

• Projects

Instead of inspecting configuration objects one by one, administrators can immediately see the full footprint of a field.

This makes it possible to:

• Identify duplicate fields created by different teams

• Detect unused fields that are no longer connected to active configurations

• Find semantic redundancies where multiple fields serve the same purpose

• Safely consolidate or remove fields with full visibility of impacted projects

As organizations approach Atlassian’s field guardrails, this level of visibility becomes critical.

---

2. Roles Usage: Understand Project Access

Project roles are another area where large Jira environments often lose clarity.

Permissions are frequently assigned through a mix of users and groups across many projects, making it difficult to understand who actually has access and why.

Roles Usage for Jira exposes the relationships between:

• Projects → Roles → Users

• Users → Roles → Projects

The app also shows whether a user is assigned:

• Directly to a role, or

• Indirectly through group membership

This distinction is often difficult to determine using Jira’s native interface but is essential for permission audits and governance.

For administrators responsible for maintaining secure and consistent access models, this visibility becomes extremely valuable.

---

3. Versions Usage: Manage Enterprise Release Complexity

Versions can also become difficult to manage in large Jira environments.

In many organizations, multiple projects use versions with the same name as part of coordinated enterprise releases. While the names may match, these versions are actually independent objects managed separately in each project.

This makes it harder to understand how releases are structured across projects.

Administrators often need to determine:

• Which versions exist across projects

• Which versions share the same name but belong to different projects

• Which versions are referenced by issues

• Which versions are no longer actively used

Versions Usage for Jira provides a consolidated overview of version usage across projects, helping administrators analyze how versions are distributed and better coordinate release management across large Jira environments.

---

Security by Design: Forge and Zero-Data Philosophy

Config Insights for Jira is built on the Atlassian Forge platform, meaning it runs entirely within Atlassian’s infrastructure and follows Atlassian’s security and data residency standards.

The apps follow a simple principle:

The most secure data is the data that is never stored.

Config Insights does not copy or store user data externally. Instead, it analyzes configuration relationships in real time and presents the results directly to administrators.

This approach ensures that sensitive configuration information always remains within the Jira environment.

---

Especially Useful for Cloud Migrations

Organizations migrating from Jira Data Center to Jira Cloud often discover years of accumulated configuration complexity.

Before migration, administrators must identify:

• unused fields

• redundant configurations

• duplicated structures

• unnecessary roles or versions

Config Insights for Jira helps administrators perform this analysis efficiently, making it easier to simplify Jira configurations before moving to Cloud.

A cleaner configuration reduces migration complexity and improves long-term maintainability.

---

Clean Your Instance Before the Limits Hit

With Atlassian introducing configuration guardrails, proactive cleanup is becoming increasingly important.

Understanding where fields, roles, and versions are used allows administrators to confidently simplify their Jira environments without breaking existing workflows or projects.

If you want to explore how these insights work in practice and start auditing your Jira configuration, you can use Config Insights for Jira.

---

Quick Jira Admin Checklist Before the Limits Hit

If you cannot answer these quickly, you’re likely already feeling configuration sprawl:

• Do we know how many custom fields we currently have?

• Do we know which fields are unused (not used in screens or workflows)?

• Do we have duplicate fields created by different teams?

• Do we have semantic redundancies (different names, same meaning)?

• Can we tell which workflows and workflow transitions reference a field?

• Can we tell which projects depend on those workflows/schemes?

This is exactly the kind of work that becomes urgent when a large instance approaches Atlassian’s field guardrails.

---

Disclosure: I am the founder of Simitech and the lead developer behind Config Insights for Jira. I built this bundle — which includes Fields Usage for Jira, Roles Usage for Jira, and Versions Usage for Jira — specifically to address the configuration sprawl and guardrail challenges discussed in this article.