# 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)
{% hint style="info" %}
PREVIEW — these fields are only used after migrating to Forge.
{% endhint %}
The following custom fields are created for Jira Cloud installations after March 2026.
| Custom field | Field key suffix | Description | Encoding |
| ---------------------- | ---------------------------- | ------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 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.
| Custom field | Description | Encoding |
| ----------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 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](https://docs.ativo.io/advanced/ativo-programs-custom-fields/field-sharing).
### Related topics
[Adding custom fields to screens](https://ativo.io/docs/fields-added-to-screens/) for Jira projects used in program and teams configurations.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.ativo.io/advanced/ativo-programs-custom-fields.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.