> For the complete documentation index, see [llms.txt](https://docs.ativo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ativo.io/getting-started/cloud-release-notes.md).

# Cloud Release Notes

This changelog contains updates for Ativo Programs for Jira Cloud. Data Center Release notes can be found [here](https://ativo.io/permalink/data-center-release-notes) instead.

### 2026-11-14

#### New features

* You can now edit the **summary** of a work item directly in Ativo.
* Epics can inherit their commitment from mapped PI objectives. This happens once an Ativo admin enables epic mapping (Plan page: View > Objectives, then Update PI objectives). A Jira admin can disable the inheritance on the Fields admin page.

#### Improvements

* Support for larger sprint goals. Click a goal to read it in full.
* The commitment level **Stretch** is now called **Uncommitted**. The values stored in the Jira field stay the same.
* In the objectives dialogs, Ativo admins now turn on **Epic mapping** with the Epic mapping button, which replaces the gear.
* On the Ativo admin pages, the top navigation now stays visible while a page loads and while it scrolls.
* The commitment level on the epic cards of the progress pages now shows its name, such as **Descoped (was committed)**, instead of its stored value.

#### Fixes

* Importing a configuration larger than 500 KB on the **Export and import** admin page no longer fails on the Forge platform.

### 2026-10-17

#### New features

* You can now edit sprint goals directly in Ativo. On the **Plan** and **Team breakout** pages, click on **View** and then on **Sprint goals**. Goals are saved to Jira sprints, so users need Jira's **Manage sprints** permission.

#### Improvements

* Ativo now reads its data from Forge storage, hosted by Atlassian, instead of from Ativo's own cloud service. This is the next step of the move of Ativo Programs to Atlassian's Forge platform.
* When Jira rejects a request, Ativo now displays more info on the cause (e.g. missing permissions)

#### Fixes

* Data Center-to-Cloud migration now preserves the links between PI objectives and their epics.

### 2026-10-03

#### Fixes

* Ativo now retries Forge requests that fail because of temporary Jira backend errors.
* The **Add or create a cross-team dependency** dialog now explains when Jira rejects a link, for example because the user lacks **Link work items** permission. It identifies which link was not saved and why.

### 2026-09-21

#### Fixes

* Ativo now retries temporary Forge connection failures, such as "Failed to fetch".

### 2026-09-19

#### Improvements

* Ativo now also saves its data in Forge storage, hosted by Atlassian, as well as in Ativo's own cloud service. This is the next step of the move of Ativo Programs to Atlassian's Forge platform.
* The Ativo REST API is now available on Jira Forge with OAuth 2.0, allowing scripts and integrations to read teams, ARTs, PIs, and PI objectives. More info in [Cloud API setup](https://docs.ativo.io/rest-api/cloud-api-setup).

#### Deprecations

* Legacy API tokens and `cloud-api.ativo.io` are scheduled to stop working on November 16th, 2026. Migrate any remaining integrations to the new REST API and revoke their legacy tokens ([Migrating from legacy API tokens](https://docs.ativo.io/rest-api/cloud-api-setup/migrating-from-legacy-api-tokens)).

### 2026-09-14

#### Fixes

* Fixed issues introduced on September 13 that could cause the message "No valid Ativo Programs license found" when opening Ativo under some conditions.

### 2026-08-29

#### New features

* Users can now share a page in **View-only** mode through **Share page view**. This hides controls that modify Ativo or Jira data and provides a compact header suitable for embedding in Confluence ([Share a page view](https://docs.ativo.io/sharing/share-a-page-view)).

#### Fixes

* Fixed a layout issue in the **Risks and impediments** dialog on the Progress pages when a work item title contained an unusually long word.

### 2026-08-22

#### New features

* The Ativo Programs administration area now has separate tabs for **Administrators**, **Issue types**, **Link types**, **Fields**, **Statuses**, **REST API**, **Audit Log**, and **Export and import**.
* Jira administrators can now open Ativo administration using **Configure** for Ativo Programs in **Manage apps**.

#### Improvements

* As the next step of the move of Ativo Programs to Atlassian's Forge platform, the pages of Ativo Programs, its administration pages included, now run on Forge, with new Jira Forge URLs. Existing bookmarks continue to work.

### 2026-06-13

#### New features

* Jira administrators can now disable automatic addition of Ativo fields to Jira screens in projects used by teams and ARTs. Use **Automatic screen updates** on the **Fields** admin page ([Fields added to screens](https://docs.ativo.io/advanced/fields-added-to-screens)).

#### Improvements

* Team, ART, and PI filters no longer require a Jira project, except for Scrum-team filters that are not based on a Jira board. Ativo can display work items returned by a filter without a project, but cannot create work items from that filter.
* PI sprints are now completed automatically the day after their end date. In **PI settings**, a status (**Past**, **Current**, or **Future**) replaces the **Completed** checkbox.

#### Fixes

* Progress metrics now use the estimates of an epic's work items planned in the PI, excluding estimates entered directly on the epic.

### 2026-06-06

#### Improvements

* Jira administrators can now customize the label used for epics, such as "Feature", using **Epic label** on the **Issue types** admin page. Ativo then uses this label instead of "Epic".
* The **Team breakout** filter bar now offers **Add linked items**, as on the **Plan** page, to include work items linked to those shown by the filter.
* PI objectives mapped to epics now show counts of red, amber, and green epics. Expanding an objective shows each epic's RAG status, with its RAG comment available on hover.
* Work items from team-managed Jira projects, which Ativo does not support, no longer appear on PI pages.

#### Fixes

* Data Center-to-Cloud migration no longer fails because of an Ativo field-version mismatch when Ativo is installed on the target Cloud site but has not yet been opened.

### 2026-05-28

#### New features

* Ativo administrators can now copy quick filters from another ART and PI using **Add from other PI** in **Configure quick filters**.
* The **Add epic** dialog on the **Plan** page now has a **Refresh** button to load epics created in Jira since the page was opened.

#### Improvements

* When creating a team from a Jira board, Ativo no longer includes a trailing "board" in the suggested team name and key. For example, a board named "Lion board" suggests the team name "Lion" and key "LION".

#### Fixes

* Field filters in **Team settings**, **ART settings**, and **PI settings** no longer briefly show "No options" while their field values are loading.
* **Find your item** now accepts work item keys from projects whose keys contain digits or underscores, such as FEAT2-1.
* Fixed an error that could stop Data Center-to-Cloud migration through the Jira Cloud Migration Assistant. Teams based on a Jira board now retain their board reference.

### 2026-05-16

#### New features

* The right-click menu for work items on the **Plan** and **Team breakout** pages now includes **Add to search filter** and **Remove from search filter**. To include their dependencies, select **Add linked items** in the filter bar.

#### Improvements

* The search filter now matches work items containing any search term instead of requiring all terms to match. Work item keys must still match in full.

#### Fixes

* Progress-page and welcome-page metrics now include work items belonging to unassigned epics in the total work, consistent with how work done was already calculated.
* Filters that select Jira projects, such as team filters, can now also be restricted to the epic issue type.

### 2026-05-08

#### New features

* On the **Plan** page, **Find your item** in the top navigation's more actions menu (**•••**) explains why a work item does or does not appear on the board. It points to the exact team, ART or PI configuration that is blocking it from appearing on the board.

#### Improvements

* **Share**, **Export**, **Feedback**, and **Help** have moved to the more actions menu (**•••**) on the right of the top navigation. **Archive** and **Unarchive** have also moved there on **ART settings** and **PI settings**.
* Sprint names now remain visible at the top of the board when scrolling on the **Plan**, **Team breakout**, and **Progress per Team** pages.

### 2026-04-25

#### New features

* In **PI settings**, Ativo administrators can now automatically select a PI's epics using a PI filter or by matching epics whose dates overlap the PI (for example, dates maintained in Jira Plans). These options are available under **PI Epic scope**. When automatic selection is used, **Add epic** is not available on the **Plan** page.
* The **ART Team-level item scope** setting in **ART settings** now includes **No refinement**, which uses all team-level items returned by the team filters. The scope can then be narrowed for each PI in **PI settings**.

#### Improvements

* **ART settings** and **PI settings** now group options into cards. **PI settings** separate the PI cadence, shared by all ARTs, from the ART-specific configuration for that PI.
* The interface now places greater emphasis on the SAFe terms **ART** and **PI**, although **program** and **period** still appear in some places. It also uses Jira's newer term **work item** instead of **issue**.

### 2026-03-30

#### Improvements

* Ativo Programs starts its gradual move to Forge, Atlassian's own platform for cloud apps.

### 2026-03-22

#### Fixes

* On new installations, saving a team or ART now adds the Ativo fields to the Jira screens of its projects.
* Fixed an issue that prevented users from setting a work item's RAG status on new installations.

### 2026-03-07

#### New features

* Jira administrators can now view the Ativo fields on the **Fields** admin page, including each field's name, ID, description, and whether it exists in Jira.

#### Improvements

* The PI filters in **PI settings** and the team-level item filter in **ART settings** now accept JQL without a Jira project or category, such as a filter on an epic field only.
* When Ativo adds fields to Jira screens, it now places them on a tab named **ART PI** instead of **Program**.

### 2020-2025 releases

For releases before 2026, see the [Ativo Programs for Jira Data Center version history](https://ativo.io/permalink/data-center-release-notes). Cloud and Data Center releases were broadly aligned during that period.
