Ativo Programs for Jira 📖 Documentation
  • Getting started
    • Quickstart guide
    • Prerequisites
    • Installation
      • Updates
    • Cheat sheet
  • Configuration
    • Permissions
    • Team
    • Program (release train)
    • Period (program increment)
    • Project and Jira (JQL) filters
  • Preparing a Program Increment (PI)
    • Program cycle
    • Feature backlog
  • Program Increment (PI) planning
    • Plan issues
    • Plan epics (features)
    • Plan dependencies
    • Raise risks and impediments
    • PI Objectives
    • Capacity
    • Team breakout
  • Scrum of scrums / Art Sync
    • Scrum of scrums and art-sync preparation
    • Progress per team
    • Progress per program
  • Cross-pi
    • Cross-PI dependencies
  • Advanced
    • Export issues, PI objectives, milestones and capacity to Excel
    • Ativo Programs custom fields
      • Field sharing
      • Ativo Program fields use PI keys since April 2023
    • Fields added to screens
    • Issue types
    • Limit permissions of suppliers
    • Jira Service Management tickets on the program board
    • Server to cloud migration
  • REST API
    • Authentication
    • Version
    • Cloud REST API Rate Limiting
    • Cloud REST API
    • Data Center REST API
  • Training
    • User training
Powered by GitBook
On this page
  • Why custom fields?
  • Which custom fields are created?
  • When are these fields created?
  • How can a user access these fields?
  • Field sharing
  • Related topics
  1. Advanced

Ativo Programs custom fields

Why 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.

Which custom fields are created?

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-TEAMLION The 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.

When are these fields created?

The fields are created upon installation of the Ativo Programs for Jira plugin.

How can a user access these fields?

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.

Field sharing

Related topics

PreviousExport issues, PI objectives, milestones and capacity to ExcelNextField sharing

Last updated 1 year ago

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. .

for Jira projects used in program and teams configurations.

Adding custom fields to screens
More info on field sharing