Configuring SLA PowerBox Metric Field

 Viewing custom fields

To view the custom fields in your JIRA system:

1. Log in as a user with the JIRA Administrators global permission.
2. Choose  > Issues. Select Fields > Custom Fields to open the Custom Fields page.
    Tip: Keyboard shortcut: g + g + start typing custom fields

 Editing a custom field

Editing a custom field allows you to change its Name (label), Description (Help text) and Search Template.

To edit a custom field:

1. Navigate to the Custom Fields page, locate the desired custom field and choose  > Edit:
   
   • The Name is the label that appears to the left of the custom field when it is displayed to a user.

   • The Description is the Help text that appears below the custom field when it is displayed in the Simple Search column.

   • Search Templates are responsible for indexing a custom field as well as making it searchable via Simple Search and Advanced Search (note that custom fields are not searchable via Quick Search). Every custom field type has a preconfigured search template, but you may select a different template using this procedure.

2. Modify the fields as desired and click Update.

 Configuring a custom field

The custom field context – also known as custom field configuration scheme is not related to the field configuration scheme – specifies the following for the custom field:

• Default Value
• Options
• The issue types and projects to which the default values and options apply

You can create multiple contexts if you need to associate different default values and options with particular projects or issue types.

Each custom field has a context named Default Configuration Scheme for ..., which is created automatically when you add your custom field.

 Context

To change the project(s) and issue type(s) to which a given Default Value and Options apply:

1. Navigate to the Custom Fields page, locate the desired custom field and choose  > Configure.
2. Locate the context named Default Configuration Scheme for ... and click the Edit Configuration link.
3. Under Choose applicable issue types, select the issue type(s) to which you want this Default Value and Options to apply. You can select any issue types if you wish.
4. Under Choose applicable contexts, select the project(s) to which you want this Default Value and Options to apply. Note that this will apply to only issues with the selected issue type(s) as above.

 Adding a new context

Adding a new context allows you to configure a custom field differently for different combinations of issue types and projects.

To add a new context:

1. Navigate to the Custom Fields page, locate the desired custom field and choose  > Configure.
2. Click the Add new context link. The 'Add configuration scheme context' page will be displayed (see below).
   
   • Under 'Add configuration scheme context', enter a 'Label' and 'Description' for your new context — these are used for administrative purposes only and will not be shown to your end-users.
   • Under 'Choose applicable issue types', select the issue type(s) to which you want this Default Value and Options to apply. You can select Any issue types if you wish.
   • Under 'Choose applicable contexts', select the project(s) to which you want this Default Value and Options to apply. Note that this will apply to only issues with the selected issue type(s) as above.

A custom field can only have one context per JIRA project. So you cannot have multiple contexts for different issue types in the same project.

 Default value

To edit the default value that a custom field contains when it is first displayed to a user:

1. Navigate to the Custom Fields page, locate the desired custom field and choose  > Configure.
2. Locate the relevant context (there will usually only be one, named 'Default Configuration Scheme for ...') and click the Edit Default Value link in the right-hand column. The 'Set Custom Field Defaults' page will be displayed and will be particular to the custom field type:
   
   • (For a Select List or Multi-Select List) Select the appropriate default value from the drop-down list.
      To clear the default of a select field, click on the current default so it is no longer highlighted and then save, as described here:Unable to De-select Default Value for Multi Select Custom Field.
   • (For a Cascading Select List) Select the appropriate default values from the drop-down lists (one for each level).
   • (For a Date field) Specify a date, or tick the check-box to make the current date the default.
   • (For other types of fields) Type the appropriate default values from the drop-down lists (one for each level).
      Certain types of custom fields, such as calculated custom fields, may not allow for defaults to be selected and will not have theEdit Default Value link.

Options

You can specify option values for custom fields of the following types:

• Select lists
• Multi select lists
• Cascading selects lists
• Radio buttons
• Multi checkboxes

You can add, remove, re-order, sort the options alphabetically, and edit the text of an option value. You can also have HTML in an option value — be sure to use complete tag pairs, and check that the HTML will display correctly.

 These options are case insensitive, so when using a select or multi-select list for a notification scheme, JIRA-ADMINISTRATORS will match the jira-administrators group. This means you cannot have both a JIRA-ADMINSITRATORS and a jira-administrators option, as they have the same name.

To edit a custom field's options:

1. Navigate to the Custom Fields page, locate the desired custom field and choose  > Configure.
2. Locate the relevant context (there will usually only be one, named 'Default Configuration Scheme for ...'), and click the Options link in the right-hand column. The 'Edit Custom Field Options' page will be displayed (see below). Here you can:
   
   • Select from the Edit parent select list drop-down to choose which list to edit. (For a Cascading Select List only)
   • Click Sort alphabetically to automatically re-order the options alphabetically.
   • Click the arrows in the Order column, or specify a number and click the Move button, to re-order the options manually.
   • Click Edit to change the text of an option.
   • Click Disable to hide an option so that it is no longer available for selection. Options that have been used cannot be removed (to preserve data integrity), but due to changing business requirements, they may become invalid over time and so you may wish to make them unavailable for new issues.
   • Click Delete to remove an option. (This will only be possible for options that have not been used.)

 User Filtering

You can limit the set of users available in your user picker field. The users can be limited to users in specific groups and/or project roles.

To filter the users in a user picker field:

1. Navigate to the Custom Fields page, locate the desired custom field and choose  > Configure.
2. Click Edit User Filtering.
3. Click Enable group or project role filtering, then specify the groups and/or roles that you want to limit the user picker to.
   The user picker will only show users that are in the groups and roles selected.
4. Click Save.

Choosing screens

To choose the Screens on which a custom field will appear:

1. Navigate to the Custom Fields page, locate the desired custom field and choose  > Screens.
2. Select the check boxes of the screens on which you wish to display this custom field.
    Note that field visibility depends on the field configuration (which is not related to the custom field configuration scheme described above). Refer to Specifying Field Behavior for more information.

Translating a custom field

You can translate the name and description of any custom field that you create into another language. You can only select from the language packs that are installed in JIRA.

To translate the field and description of a custom field to another language:

1. Navigate to the Custom Fields page, locate the desired custom field and choose  > Translate.
2. Choose the language pack that this custom field translation will belong to (e.g. French) and