Configurations overview: Understanding Jira schemes
As a Jira administrator, you are responsible for a large number of projects with different settings and views. The more projects you manage, the greater the risk of configuration conflicts — and the more difficult it is to keep track of them all.
For example, you manage a project whose workflow you also want to use for another project. How do you proceed? Or you have defined that the field "Editor" is mandatory in screen A, but irrelevant in screen B. What do you do? Or you want to change the selection of the issue types for several masks afterwards. Can't you do that easily and quickly?
Yes, you can.
For all these use cases and questions, there is one answer: Jira schemes. When configuring Jira, they are an important part, but often cause confusion. However, that doesn't have to be.
In this article, we'll give you the ultimate overview of Jira schemes and finally bring clarity to this complex topic.