ISO Atlassian Blog

The Current Situation

Until now, required fields were defined in Jira and then assigned to the respective field configurations. These were in turn bundled into field configuration schemas and linked to scopes to determine which fields are displayed where.

However, the original goal—greater flexibility and reusability—leads to the following challenges in practice:

Jira schemas are a complex and sometimes difficult to understand area of responsibility. And not only for new Jira administrators, but also for Atlassian veterans. It is not uncommon for a Jira admin to have to laboriously work their way through many different schemas when a customization is required. With larger and historically grown systems, there can even be hundreds of schemas.