Comment on page
Ativo Programs custom fields
Ativo programs stores data on issues to track the program planning in the program increment.
In order to make this data available in Jira outside Ativo Programs, it is stored on custom fields on the issue itself.
The following custom fields are created when installing Ativo Programs:
- Program This custom field is created for future use.
- Program team Contains the team in the lead for an epic. This field contains multiple entries, one per program increment. An entry is by default formatted as
Programkey-PeriodKey-TeamKey. Example:PGRM1-2024Q1-TEAMLIONThe encoding scheme is different if field sharing is enabled. - Program period Contains the period in which the epic is planned. This field contains multiple entries, one per program increment. An entry is by default formatted as
Programkey-PeriodKey. Example:PGRM1-2024Q1 - Program Baseline Sprint Contains the sprint in which the epic is planned during the PI planning. This field contains multiple entries, one per program increment. An entry is by default formatted as
Programkey-PeriodKey.SprintId. Example:PGRM1-2024Q1.2 - Program Commitments Contains the commitment that is given to an epic. This field contains multiple entries, one per program increment. An entry is by default formatted as
Programkey-PeriodKey-CommitmentLevel. Example:PGRM1-2024Q1-committed - Program RAG Contains the Red Amber Green indication given to an issue.
- Program RAG Comments Contains the comments given that explain why the issue is in a Green, Amber or Red state. This usually contains the impediments and risks.
The fields are created upon installation of the Ativo Programs for Jira plugin.
A user can use these fields in Jira. JQL queries can be performed via Issues > Search for issues.
If the custom fields are added to a Jira project, then the user can also access them on the related issues itself.
You can configure Ativo to share 'commitment', 'added to period', 'baseline sprint' and 'team in the lead' issue fields between programs in a period. This also affects the way how fields are encoded. More info on field sharing.