Commonly-Used Keywords

The following table lists some common keywords you may sometimes see:

Keyword	Usage	Notes
collab:	Indicates that the ticket has been authored by someone who is not 100% employed by the Met Office	Use form collab:<orgname> e.g. collab:niwa, collab:oxford
blocks:	Code change is blocking the numbered ticket from going on to the project’s trunk	e.g. blocks:#1234 Not used by LFRic Core as they have a “blocked by” item in their ticket options.
blockedby:	Code change is blocked by the numbered ticket from going on to the project’s trunk	e.g. blockedby:#6789 Not used by LFRic Core as they have a “blocked by” item in their ticket options.
kgo	Indicates the change requires new kgo installing (change in answers); See KGO.	Includes when a new job is added to the project’s rose stem suite
macro	Indicates the change includes an upgrade macro
doc	Indicates that the change includes documentation updates
SR:<name>	Denotes person who will SciTech review the change	Optional for reviews outside of the SSD team; Added later in development
CR:<name>	Denotes person who will CodeSys review the change	Added when the reviewer is assigned.
linked:um linked:jules linked:core linked:apps linked:ukca	Indicates that the change has a linked ticket with the code base specified by the keyword. These are just examples - all linked repositories should be included.