Documentation for JIRA 4.2. Documentation for other versions of JIRA is available too.
On this page:
A Field Configuration provides the ability to change field behaviour. For each field, a Field Configuration specifies:
A Field Configuration specifies individual behaviour for every issue field, including both standard fields and custom fields.
You can create multiple Field Configurations (see below). You can then associate different Field Configurations with different issue types by creating a Field Configuration Scheme. Once created, a Field Configuration Scheme can be associated with one or more projects, allowing you to control field behaviour on a per project, per issue type basis.
For information about placing fields on Screens, and using Screen Schemes to associate screens with issue operations, please see the Overview.
To change the behaviour of fields, you first need to navigate to the Field Configuration. The way this is done depends on the edition of JIRA:
The "View Field Configuration" page lists all system and custom fields in a table as shown below. The "Operations" column lists all the operations that are available for each field. These operations could be:
Screenshot: Field Configuration - View Issue Fields
Fields can be given descriptions to better identify the meaning of the field. These descriptions are usually displayed under the field on the creation of an issue and whenever it is edited. An example of this, is shown below.
To edit the description of a field:
If your organisation or project has no use for a particular field, you have the option to hide it. Hiding a field will ensure that the the field does not appear on any Screens (i.e. issue operation Screens, workflow transition Screens) where the Field Configuration applies.
Hiding a field in the Field Configuration is distinct from not adding a field to a Screen. Fields hidden through the Field Configuration will be hidden in all applicable Screens, regardless of whether or not they have been added to the Screen.
For fields that have a default value:
If the field is hidden in the Field Configuration, then it will not receive a value when an issue is created, regardless of whether the field is present on the 'Create Issue' screen(s). (The following fields can have a default value: 'Resolution'; 'Status'; 'Priority'; 'Issue Type'; custom fields.)
To hide a field:
The fields 'Summary' and 'Issue Type' cannot be hidden and as such there is no 'Hide' option available for these fields.
注意:
If you hide the 'Fix For Version' field, the Change Log and Road Map reports will not work.
Certain fields within your organisation may be compulsory for issues. In this case you can set a field to be required, so that JIRA validates that the field has been given a value whenever an issue is edited. If a required field has not been given a value, JIRA will return an error informing the user that the field should be filled, e.g.:
If you set a field to "required", ensure that the field is present on your 'Create Issue' screen(s). Note that in you can have different field configurations for different projects and issue types (see 'Associating field behaviour with Issue Types'); so you need to ensure that all "required" fields are present on the 'Create Issue' screens for all associated projects and issue types (see 'Associating screens with Projects and Issue Types'). There is a feature request at JRA-5783 to make a field required only on one transition. Please watch it for status updates.
フィールドを必須にするには、次の操作を実行します。
Fields that are hidden cannot be set to required. Making a hidden field required will make it "shown" as well.
Before you begin, please read 'Configuring Renderers', paying particular attention to the section 'Implications for JIRA operations'.
The "View Field Configuration" page indicates which renderers are currently enabled for all renderable fields.
In the screenshot "Field Configuration - View Issue Fields" (above), you will notice the grey text 'Wiki Style Renderer' under the Description field's name in the leftmost column. This indicates that the field is currently configured to use the Atlassian Wiki Renderer. The grey text 'Default Text Renderer' under the Comment field's name indicates that the field is currently configured to use the Default Text Renderer.
To change the renderer type for a specific field, click on the 'Renderers' link in the 'Operations' column of the screen for the field you want to change. This will take you to a page where you will have the option to select a renderer from all configured and available renderers.
As shown above, this page will warn you if there are issues that will be affected by the change. If no issues will be affected then the warning does not show. From this page, choose the renderer you wish to use and click 'Update'. You are then presented with a confirmation page, shown below.
Click the 'Update' button to finish setting the new renderer on the field.
Changing the renderer only affects the display of the issue data that exists in the system. You can therefore toggle back and forth between renderer types safely.
別のプロジェクト課題タイプで使用するための複数のフィールド設定をすることができます。
Multiple field configurations are organised into Field Configuration Schemes based on issue type. A scheme can be associated with one or more projects, allowing you to control fields on a per project per issue type basis. See Associating Field Behaviour with Issue Types for details.
To create, edit, delete and copy individual field configurations, go to the "View Field Configuration" page as follows:
When JIRA is installed, the 'Default Field Configuration' is created automatically. All new projects are associated with this configuration. This configuration is also used for projects that are not associated with a Field Configuration Scheme..
It is not possible to delete the Default Field Configuration.
A newly created Field Configuration will not take effect until it has been activated (see below).
A newly created Field Configuration will not take effect until it has been activated (see below).
To activate a Field Configuration:
For details of both procedures, see 'Associating field behaviour with Issue Types'.