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:

  • Program
    This custom field is created for future use.
  • Program team
    Contains the team in the lead for an epic. This field can contain multiple entries, one per period (program increment).
  • Program period
    Contains the period in which the epic is planned. This field can contain multiple entries, one per period (program increment).
  • Program Baseline Sprint
    Contains the sprint in which the epic is planned during the PI planning. This field can contain multiple entries, one per period (program increment).
  • Program Commitments
    Contains the commitment that is given to an epic. This field can contain multiple entries, one per period (program increment).
  • 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.

Related topics

Adding custom fields to screens for Jira projects used in program and teams configurations.