Documentation for JIRA 4.2. Documentation for other versions of JIRA is available too.
On this page, we show you how you can configure your custom field after you've created them.
For most custom fields, you can configure its default values and set the options for lists. When you click on the configure link, you'll be faced with a page similar to the one below.
You'll notice that there is a configuration scheme named Default Configuration Scheme for.... This is the configuration scheme created automatically by JIRA when you initially added your custom field. The Applicable contexts for scheme refers to context that this scheme will be applied to; which projects & issue types the defaults and options will be displayed. For most people this will be only thing you need to know about custom field configuration schemes. You can edit the context by clicking Edit configuration or the edit icon on the top left hand corner.
Here you can edit the label and description of the configuration scheme. These are used for administrative purposes only and isn't shown to the end users. You can also change the context that this scheme is to be applied to here. It's now easier than ever to change the projects or issue types for the configuration context.
Select lists, multi select lists and cascading selects lists can have their options manipulated. You can add, remove and sort the options alphabetically. You can also have HTML in an option value. Be sure to use complete all tag pairs and ensure that it will display correctly.
Click the Edit defaults to modify the default value of a custom field for this configuration scheme. Setting the defaults will take you to a screen that is particular to the issue type. Certain custom fields such as calculated custom fields may not allow for defaults to be selected and will not have the "edit defaults" link. Date fields offer a checkbox to make the default the current date. To clear the default of a select field, click Edit defaults and then click on the current default so it is no longer highlighted and then save, as described
Since JIRA 3.2, it is now possible to configure a custom field differently for different issue types and project combinations. This can be achieved through configuring different custom field schemes.