On this page:
In this section:
- Configuring Built-in Fields
- Adding a Custom Field
- Specifying Field Behaviour
- Defining a Screen
Diagram: How Fields, Screens and Workflow interrelateGliffy
To help you tailor JIRA to your organisation's needs, JIRA enables you to manipulate the display and behaviour of issue fields ('Summary', 'Description', 'Issue Type', etc). You can:
- Change a field's description
- Make a field hidden or visible
- Make a field required or optional
- Add your own values for 'Issue Type', 'Priority', 'Resolution' and 'Status'
- Create new 'custom' fields
- Enable a rich text renderer for (some) fields
- Position fields on a screen
- Choose which screen should be displayed for each issue operation (e.g. 'Create Issue', 'Edit Issue') or workflow transition (e.g. 'Resolve Issue', 'Close Issue')
Some key JIRA concepts include:
- Field Configuration --- a set of definitions for all fields, comprising: each field's description; whether each field is hidden or visible; whether each field is required or optional; and what type of renderer to use for each text field.
- Screen — defines which fields are present on a screen, and their order. (Note that a hidden field can be present on a screen, but will still be invisible.)
- Screen Scheme — associates different screens with different issue operations (e.g. 'Create Issue', 'Edit Issue', 'View Issue').
- Issue Type Screen Scheme — associates Screen Schemes with issue types and projects. This allows you to specify different Screens for the same operation (e.g. 'Create Issue') in the same project for issues of different types. For example, you could use one screen when creating an issue of type 'Bug', and a different screen when creating an issue of type 'Task'.
- Field Configuration Scheme — associates Field Configurations with issue types and projects. This allows you to specify different field behaviour for the same field in the same project for issues of different types.
- Issue Type Scheme — associates issue types with projects.