Page History

Epic Colour is the colour assigned to the epic. This is auto-assigned initially then can be changed via a dropdown on the colour box on the epic (in

This field was introduced in 

This field is not configurable via the

Epic Name (editable) is a short name that is used to identify an epic (see Creating an Epic).

This field was introduced in 

This field is not configurable via the

Epic Link is used to determine the parent epic for an issue. This is a non-editable field; it is set by GreenHopper when you add/remove an issue to/from an epic.

Searchable via

This field was introduced in 

This field is not configurable via the

Epic Status is used to exclude completed epics from being displayed in Plan mode.

This field was introduced in 

The Epic Status field can have one of the following values:
'ToDo' - indicates that the epic is currently open. The epic will be visible in the board.
'In Progress' - reserved for future enhancements (not used at present).
'Done' - indicates that the epic is completed. The epic will not appear in the board.

This field is not configurable via the

See Flagging an Issue (or if you are using the Classic boards, please see Setting up a Flagging Field).

See also Enabling Ranking (or if you are using the Classic Planning Board then see Setting up a Ranking Field and Specifying your Project Templates).

Please ensure that your JIRA instance contains only one custom field called Rank, and that the Rank field is assigned to the global context (i.e. not to specific issues or projects).

This field is not configurable via the

Searchable via

This field was introduced in 

This field is not configurable via the

This field is of type 'Number' and is available to issue types 'Story' and 'Epic'.

• By default, the Story Points field is only available to issues of type 'Story' or 'Epic' (not 'Bugs' etc) — you can change this by:
  
  • Associating the Story Points field with other issue types (see the JIRA 

    Include Page
    _custom field context _custom field context

    documentation).
  • Specifying which screens the Story Points field will be displayed on (see the JIRA documentation on 

    Include Page
    _Defining a Screen _Defining a Screen

    ).
• On the Classic Planning Board, this custom field is used in the Scrum template, or any template you configure, and can be displayed on the 'Card', 'Summary' and 'List' view; to ensure it is available when creating cards, it must be present in the Card Style.