# Ativo Programs for Jira 📖 Documentation

## Ativo Programs documentation

- [Quickstart guide](https://docs.ativo.io/getting-started/quickstart-guide.md): In this quick start guide, we will discover how to install Ativo Programs for Jira, and configure the first Program Increment in 5 steps.
- [Prerequisites](https://docs.ativo.io/getting-started/prerequisites.md): Validate if the following prerequisites are met before installing and configuring Ativo Programs
- [Installation](https://docs.ativo.io/getting-started/installation.md)
- [Updates](https://docs.ativo.io/getting-started/installation/updates.md): Update Ativo Programs to the latest version.
- [Cheat sheet](https://docs.ativo.io/getting-started/cheat-sheet.md): This page describes the main steps of a program increment planning and delivery.
- [Permissions](https://docs.ativo.io/configuration/permissions.md)
- [Team](https://docs.ativo.io/configuration/team.md): A team is a closely collaborating group of people, contributing to one or more programs (Agile Release Trains - ARTs).
- [ART (program)](https://docs.ativo.io/configuration/art-program.md): An Agile Release Train (ART) or program is a temporary organizational structure, used to deliver business value. It contains a set of agile teams that work closely together.
- [PI (period)](https://docs.ativo.io/configuration/pi-period.md): A Planning Interval (PI) or period, is a timebox in which an increment of an ART is planned and delivered.
- [Project and Jira (JQL) filters](https://docs.ativo.io/configuration/project-and-jira-jql-filters.md): The scope of Teams,  Programs and Periods (Program increments) are defined based on project and Jira (JQL) filters
- [PI cycle](https://docs.ativo.io/preparing-for-a-pi/pi-cycle.md)
- [Feature backlog](https://docs.ativo.io/preparing-for-a-pi/feature-backlog.md): Each program has a backlog list of features (epics).  Features are in Jira encoded as Epics. In this documentation, feature and epic terms are used interchangeably.
- [Plan work items](https://docs.ativo.io/pi-planning/plan-work-items.md): Teams plan their stories during the breakout session of the PI Planning meeting. The planning of stories can be done in the project backlog of the team, or directly on the program board.
- [Plan epics (features)](https://docs.ativo.io/pi-planning/plan-epics-features.md)
- [Plan dependencies](https://docs.ativo.io/pi-planning/plan-dependencies.md)
- [Raise risks and impediments](https://docs.ativo.io/pi-planning/raise-risks-and-impediments.md)
- [PI Objectives](https://docs.ativo.io/pi-planning/pi-objectives.md)
- [Capacity](https://docs.ativo.io/pi-planning/capacity.md)
- [Team breakout](https://docs.ativo.io/pi-planning/team-breakout.md): Use the team breakout page to conveniently view the PI plan from the perspective of a specific team.
- [Scrum of scrums and art-sync preparation](https://docs.ativo.io/scrum-of-scrums-art-sync/scrum-of-scrums-and-art-sync-preparation.md)
- [Progress per team](https://docs.ativo.io/scrum-of-scrums-art-sync/progress-per-team.md)
- [Progress per program](https://docs.ativo.io/scrum-of-scrums-art-sync/progress-per-program.md)
- [Cross-PI dependencies](https://docs.ativo.io/cross-pi/cross-pi-dependencies.md): The cross-PI page shows dependencies between ARTs
- [User training](https://docs.ativo.io/training/user-training.md)
- [Share a page view](https://docs.ativo.io/sharing/share-a-page-view.md): Share the exact page you are looking at — including the ART, PI, team, filters and view options — with a single link. The data stays live: whoever opens the link sees the current state of the plan.
- [Export issues, PI objectives, milestones and capacity to Excel](https://docs.ativo.io/sharing/export-issues-pi-objectives-milestones-and-capacity-to-excel.md)
- [Cloud API Setup](https://docs.ativo.io/rest-api/cloud-api-setup.md)
- [Migrating from legacy API tokens](https://docs.ativo.io/rest-api/cloud-api-setup/migrating-from-legacy-api-tokens.md)
- [Sample token exchange script](https://docs.ativo.io/rest-api/cloud-api-setup/sample-token-exchange-script.md)
- [Data Center API Setup](https://docs.ativo.io/rest-api/data-center-api-setup.md)
- [REST API Endpoints](https://docs.ativo.io/rest-api/rest-api-endpoints.md)
- [API Version](https://docs.ativo.io/rest-api/api-version.md)
- [Ativo Programs: custom fields](https://docs.ativo.io/advanced/ativo-programs-custom-fields.md)
- [Field sharing](https://docs.ativo.io/advanced/ativo-programs-custom-fields/field-sharing.md): Share 'commitment', 'added to period', 'baseline sprint' and 'team in the lead' issue fields between programs in a period
- [Ativo Program fields use PI keys since April 2023](https://docs.ativo.io/advanced/ativo-programs-custom-fields/ativo-program-fields-use-pi-keys-since-april-2023.md): 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.
- [Fields added to screens](https://docs.ativo.io/advanced/fields-added-to-screens.md)
- [Issue types](https://docs.ativo.io/advanced/issue-types.md)
- [Limit permissions of suppliers](https://docs.ativo.io/advanced/limit-permissions-of-suppliers.md)
- [Jira Service Management tickets on the program board](https://docs.ativo.io/advanced/jira-service-management-tickets-on-the-program-board.md)
- [Server to cloud migration](https://docs.ativo.io/advanced/server-to-cloud-migration.md)
- [Cloud Forge migration](https://docs.ativo.io/advanced/cloud-forge-migration.md): Ativo Programs is migrating to the new Jira Forge platform in 2026