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 change?
  • What changes?
  • Gradual change
  • Impacts for users?
  • When change?
  1. Advanced
  2. Ativo Programs custom fields

Ativo Program fields use PI keys since April 2023

The way how data is saved on Ativo Program fields changed in April 2023. People who use Ativo Programs field data directly might need to update their filters.

PreviousField sharingNextFields added to screens

Last updated 1 year ago

You can opt-out of this change by enabling .

Why change?

In our previous data model, data was saved with the period key only. This caused limitations when features are used in multiple program increments on the same period. To solve this problem, we have to change the way data is saved on the Ativo Programs fields in Jira.

What changes?

The way how the following are formatted, changes:

  • Program team An entry is now formatted as Programkey-PeriodKey-TeamKey . Example: PGRM1-2024Q1-TEAMLION

  • Program period An entry is now formatted as Programkey-PeriodKey . Example: PGRM1-2024Q1

  • Program Baseline Sprint An entry is now formatted as Programkey-PeriodKey.SprintId . Example: PGRM1-2024Q1.2

  • Program Commitments An entry is now formatted as Programkey-PeriodKey-CommitmentLevel. Example: PGRM1-2024Q1-committed

Gradual change

Data will only be updated to the new format when taking an action in Ativo Programs (e.g. updating a team in the lead in Ativo). Entries using the old data format will be gradually replaced with new entries..

There is hence no bulk data migration needed.

Ativo Programs continues to accept the old data format. If an Ativo Programs field contains both entries in the new and old data format, entries in the new data format will take precedence.

Impacts for users?

There is no impact for users that work in Ativo Programs. The change is not visible in the UI itself.

There is an impact for power users who:

  • Use Ativo Programs fields directly in Jira filters / reports. Those users need to change their JQL queries to include the new data format. Example: the old "Program Period[Labels]" = 2023Q1 JQL query would first become "Program Period[Labels]" in (2023Q1, PROGRAMONE-2023Q1) to include the program increment key(s) (program key + period key combined) instead. Over time, only the new keys would be needed. E.g. "Program Period[Labels]" = PROGRAMONE-2023Q4.

  • Build automation scripts using Ativo data. They will need to update the way data is read or updated according to the new format.

When change?

The above changes are effective on April 23rd 2023 (on the Jira cloud platform), and after installing Ativo Programs version 3.1 (Jira Server / Data Center platform).

More questions? Contact .

field sharing
Ativo Programs fields
Ativo support