...
Each custom field has a so-called “Default Configuration Scheme”, which the Jira administrator can view by selecting the Configure option in the menu next to the listing of a custom field. The Default Configuration Scheme specifies two things that are relevant to the use of CM4JeaseContext:
default value - This is the value (if any) that the custom field has when an issue is first created.
options - These are the possible values the custom field may have if it is of a type that has a defined list of values.
...
The configuration of project-specific contexts normally requires global Jira administration permission. This means that if a project wants to create such a context, or to modify an existing context, it has to turn to a Jira administrator, which introduces delay and creates a burden for both the Jira administrator and the project administrator. A better solution is to enable the project administrators to create and maintain the project-specific contexts independently of the Jira administrator - which is precisely the functionality that CM4J easeContext provides.