JIRA can become cumbersome to manage when used by many users for different use cases, especially custom schemes that are shared among projects. Imagine a case where a project manager asks you to remove a certain custom field from one of his project's screens, but you accidentally remove it from other projects too. In this chapter, we will discuss the best practices JIRA administrators can employ to maintain their instances.
In this chapter, we will cover the following:
A word of caution before modifying default schemes and configurations
The JIRA customization process
Using project context to assign different options in multiple projects
Creating too many custom fields—a factor in slow performance
Choosing a custom field type wisely
Defining permissions
JIRA's Audit Log
Adding the announcement banner
Adding an introduction
Performing regular indexing
Final tips