Afield settingsdefines the behavior ofall fieldsavailable in your Jira installation, including Jira's own "fixed"/"built-in" fields (known as "system" fields) andthe custom fields.
A specific field setting for each field:
ANDDescriptionthat appears below the field when editing an issue
if the field isescondidoÖvisible
if the field isnecessary(that is, the field is validated to ensure that a value has been assigned) orOptional
(only for text fields) thatrendererto use
You must log in as a user for all of the following proceduresAdministratorworldwide permission.
Typically, when you define field behavior for one or more Jira projects and the fields used by issue types in those projects, you start by adding one or more new field settings (see below). It then proceeds to modify the behavior of each field in these new field configurations.
A new field setting must be added for each project and issue type combination that requires the presence of specific fields and/or fields expressing unique behavior. You can map each new field setting to a different issue type via afield structure scheme. A field configuration schema can then be associated with one or more projects.
Manage multiple field settings
You can create multiple field configurations to use for separate projects and problem types.
Various field configurations are organized into field configuration schemas that associate field configurations with problem types.
A blueprint can then be linked to one or more projects, allowing you to track fields by project and issue type. To seeAssociation of field behavior with problem typesfor more information.
About default field settings
When Jira is installed, theDefault field settingsit will be created automatically. All new projects are assigned to this configuration. This configuration is also used for projects that are not assigned a field configuration schema.
Unable to edit or delete themDefault field settings.
Add a field configuration
To choose>romances.
(Video) How to Configure Field Configurations in Jira | Atlassian JiraLowCAMPOS, to choosefield settingsto see all field settings.
click on itAdd field settingsbutton to open theAdd field settingsdialog box.
complete aAdd field settingsdialog box:
Name— Enter a short sentence that best describes your new field settings.
Description(optional but recommended)— Enter a sentence or two to describe when to use this field setting.
click on itAdd toto add your new field configuration to Jira. Once you've added your new field settings, you can start changing the behavior of your fields (below). You will be taken directly toShow field settingsPage where you can change the behavior of fields in your new field configuration. See Changing Field Behavior (from Step 4) below for more details.
A newly created field setting will not take effect until you:
Associate your new field settings with one or more issue types.
Associate this field configuration with one or more projects.
verAssociation of field behavior with problem typesfor more information.
Edit a field configuration
ANDTo editLink allows you to change theNamejDescriptionthe field configuration, not individual fields. If you want to change individual fields, see Changing Field Behavior (below).
To choose>romances.
LowCAMPOS, to choosefield settingsto see all field settings.
click on itTo editnext to the field setting you want to edit.
About itEdit field settingsedit field settingsNamejDescription.
Delete a field setting
You can only delete a field configuration that is not associated with a field configuration schema. HeextinguishThe link is not available for field configurations associated with one or more field configuration schemes.
To delete a field configuration:
To choose>romances.
LowCAMPOS, to choosefield settingsto see all field settings.
click on itextinguishnext to the field setting you want to delete.
Copy a field configuration
To choose>romances.
LowCAMPOS, to choosefield settingsto see all field settings.
click on itcopy ofnext to the field setting you want to copy.
About itCopy field settingspage, specify itNamejDescriptionso that the settings in place are copied.
Change field behavior
To change how fields behave in Jira, you need to change the field settings in which those fields are defined.
To choose>romances.
LowCAMPOS, to choosefield settingsto see all field settings.
Find the area of interest settings and click the buttonTo configureLink to open theShow field settingsPage listing all system and custom fields in your Jira installation for this field configuration.
insideTo behaveColumn, you can perform the following actions for each field:
To edit— Change the field description (for example, help text).
hide show— Hide or show the field.
Mandatory/Optional— Specify whether a field is required (that is, it must receive a value whenever a field is edited) or optional.
renderer— Change a field's renderer (seeconfigure renderersfor more information).
Edit a field description
Fields can be provided with descriptions to better understand the meaning of the field. These descriptions usually appear below the fields they are associated with when creating or editing an Issue.
To choose>romances.
LowCAMPOS, to choosefield settingsto see all field settings.
Find the area of interest settings and click the buttonTo edit.
Change the description however you like.
click on itTo updateButton to save changes.
Hide or show a field
If your organization or project doesn't use a certain field, you have the option to hide it. Hiding a field ensures that the field does not appear on screens (for example, broadcast execution screens, workflow transition screens) where the field's settings are applied.
Hiding a field in field settings is different than not adding a field to a screen. Fields that are hidden by field settings are hiddennoApplicable screens, whether added to the screen or not.
For fields that have a default value: If the field is hidden in the field configuration, it will not receive a value when creating an issue, regardless of whether the field exists in the field.create troublescreen(s). (The following fields can have a default value: Resolution, Status, Priority, Issue Type, Security Level, and Custom Fields.)
FelderSummaryjArt des Problemscannot be hidden and as such there are noTo hideOption available for these fields.
if you hide themcorrect versionsThe Change Log Report field does not work.
To hide or show a dashboard on any screen in your Jira site:
Follow the first three steps above (under Change field behavior) to access field settings for which fields you want to hide or show.
Do one of the following:
If you no longer want to display a field through the Jira UI, clickTo hideLink associated with this field. You can make this field visible again at any time by clicking onShowShortcut.
If you want to show a field (which is currently hidden) from the Jira UI, clickShowLink associated with this field. You can hide this field again at any time by clicking onTo hideShortcut.
Make a field required or optional
Certain fields in your organization may be required for issues. In that case, you can make a field mandatory so that every time Jira edits an issue, it checks to see if a value has been assigned to the field. If a required field does not have a value assigned, Jira will return an error informing the user that the field must be completed.
Follow the first three steps above (under Change Field Behavior) to access settings for fields you want to make required or optional. When viewing a field configuration, mandatory fields have this indication next to their name.
(Video) Creating Positive Behavior Support PlansDo one of the following:
To make a field mandatory when used through the Jira UI, clickNecessaryLink associated with this field. The textNecessaryappears next to the field name. Hidden fields cannot be required.
To make a field optional, clickOptionalLink associated with this field. HeNecessarythe text next to the field name disappears.
when you make a fieldNecessary, check if the field is present in yourcreate troubleProcess):
Note that you may have different field settings for different projects and issue types (seeAssociation of field behavior with problem types), so you need to make sure that allNecessaryThe fields are present increate troubleScreens for all related projects and issue types (seeAssigning Operations and Issue Screens to a Issue Type).
Note that there is a feature requirement (JRA-5783) to require a single transition field. If you're interested, watch this issue for status updates.
Change a field's renderer
Before changing the renderer for a specific field, readconfigure renderers, with special attention toImpact on Jira operationsSection.
To choose>romances.
LowCAMPOS, to choosefield settingsto see all field settings.
Find the area of interest settings and click on itrenderer.This will take you to a page where you have the option to select a renderer from all the configured and available renderers.
Select the renderer you want to use and click on itTo update.
When viewing a field configuration (see above), theNameThe column indicates which renderers are currently enabled for each renderable field, and the current renderer is shown in parentheses immediately below the field name.
Changing the renderer only affects the appearance of the content of a Jira fieldunfoldedor as a userinteractwith multiple selection field: does not affect the issue data available in the system. This lets you safely switch between renderer types.