Gal emphasizes the need for access to methods and tools that enable Jira administrators to explore and understand the relationships between various elements within the Jira instance. As they manage the configuration changes requested by users, they need to evaluate the impact of any changes they make on the overall performance, user experience, and functionality of the Jira instance.
For example, Gal notes that even small changes like modifying the name of a custom field can disrupt the functionality of Jira filters, and Jira does not alert administrators when a custom field is modified. Modifying custom fields can also impact automation rules, and as the number of filters and automation rules increases, checking them manually is not practical.
Gal recommends planning, exploring, and documenting changes, testing them in a staging environment, and closely monitoring the system after the configuration changes have been implemented.
Administrators should identify the required changes, consider their impact on Jira workflows, filters, automation rules, screens, and other Jira elements and explore the Jira instance to find all dependencies related to the changes.