Ativo Programs: custom fields
Why custom fields?
Ativo Programs stores data on Jira issues to support planning and tracking within a PI.
To make this data available in Jira outside Ativo Programs, it’s stored in custom fields on the work item itself.
Custom fields on Jira Cloud Forge (new)
PREVIEW — these fields are only used after migrating to Forge.
The following custom fields are created for Jira Cloud installations after March 2026.
ART PI
ativo-art-pi
PI(s) this epic (feature) is planned in.
An entry is formatted as ProgramKey-PeriodKey . Example: PGRM1-2024Q1
ART PI Team
ativo-art-pi-team
Team in the lead for delivering this epic (feature) per PI.
An entry is formatted as ProgramKey-PeriodKey-TeamKey . Example:
PGRM1-2024Q1-TEAMLION The encoding scheme is different if field sharing is enabled.
ART PI Baseline Sprint
ativo-art-pi-baseline-sprint
Baseline (planned end) sprint for this epic (feature) per PI.
An entry is formatted as ProgramKey-PeriodKey.SprintId . Example: PGRM1-2024Q1.2
ART PI Commitment
ativo-art-pi-commitment
Commitment level for this epic (feature) per PI.
An entry is formatted as ProgramKey-PeriodKey-CommitmentLevel. Example: PGRM1-2024Q1-committed
ART PI Supplementary
ativo-art-pi-supplementary
Additional PI(s) this work item is added to (outside parent-child links).
Same as ART PI
ART RAG
ativo-art-rag
RAG status (Red/Amber/Green) for this work item.
Red, Amber or Green
ART Risk or Impediment
ativo-art-risk-impediment
Current risk or impediment affecting this work item.
Text
Custom fields on Jira Data Center and Jira Cloud Connect
The following custom fields are created for Jira Data Center installations and Jira Cloud (Connect) installations before March 2026.
Note for Jira Cloud: the Forge fields above are also created, but not used if the site’s initial Ativo Programs installation was before March 2026.
Program Period
PI(s) this epic (feature) is planned in.
An entry is formatted as ProgramKey-PeriodKey . Example: PGRM1-2024Q1
Program Team
Team in the lead for delivering this epic (feature) per PI.
An entry is formatted as ProgramKey-PeriodKey-TeamKey . Example:
PGRM1-2024Q1-TEAMLION
The encoding scheme is different if field sharing is enabled.
Program Baseline Sprint
Baseline (planned end) sprint for this epic (feature) per PI.
An entry is formatted as ProgramKey-PeriodKey.SprintId . Example: PGRM1-2024Q1.2
Program Commitments
Commitment level for this epic (feature) per PI.
An entry is formatted as ProgramKey-PeriodKey-CommitmentLevel. Example: PGRM1-2024Q1-committed
Program
Additional PI(s) this work item is added to (outside parent-child links).
Same as Program Period
Program RAG
RAG status (Red/Amber/Green) for this work item.
Red, Amber or Green
Program RAG Comments
Current risk or impediment affecting this work item.
Text
When are these fields created?
The fields are created when the Ativo Programs for Jira app is installed.
How can a user access these fields?
Users can query these fields using JQL in Jira via Issues → Search for issues (or the issue navigator).
If the custom fields are added to the relevant screens in a Jira project, users can also view and edit them directly on work items.
Field sharing
You can configure Ativo to share 'commitment', 'added to period', 'baseline sprint' and 'team in the lead' issue fields between programs in a period (PI). This also affects how fields are encoded. More info on field sharing.
Related topics
Adding custom fields to screens for Jira projects used in program and teams configurations.
Last updated