Fields, Screens, and Schemes (Info and Configuration)

Field configurations

set of definitions for all fields
-description
-visible or hidden
-required or optional
-renderer

screen

defines which fields are present on a screen and their order

screen scheme

associates different screens with different issue operations
-create issue
-edit issue
-or view issue

workflow

-defines the statuses and transitions with different issue operations

field configuration scheme

-associates field configurations with issue types
-these schemes are applied to projects

field configuration schemes allow you to

define different fields for each issue type in a project

issue type screen scheme

-associates screen schemes with issue types
-applied to projects

what do issue type screen schemes allow

-to specify different screens for a particular operation for each type of issue in a project
-different screen for bug creation than for story creation

workflow scheme

associate workflows with issue types
-applied to a project

issue type scheme

-applied to projects
-defines or restricts which issue types are available in a project

you can't reuse an issue type scheme across projects

false

issue priority field

allow you to set hierarchical priority for issues in a project
-priority levels are customizable and rearrangeable

should you have a resolution named unresolved?

NO jira will read this as resolved regardless of the name

how do you add a resolution?

Go to system settings>issues>resolutions> name and describe the resolution

what fields are considered the issue constants:

-issue type field
-status field
-resolution field
-priority field

what fields can be translated?

the issue constants

sets of field configurations are organized into....

field configuration schemes