Release notes for 11.29.X

The Atlassian Jira Align team is pleased to announce Jira Align v.11.29.

These features for 11.29 were released to environments on the continuous release track on September 11, 2026, in version 11.29.0. The features will be released to environments on the bundled release track on September 25, 2026, in version 11.29.1.

• Coming soon
• Enhancements and features
• Bug fixes

Coming soon

Upcoming end-of-support status for classic epics grid

With the launch of the new epics grid page experience, we’re signaling a change to the original epics grid page. As of version 11.30, scheduled to deploy to sandbox environments on October 9, 2026, and then production environments on October 23, 2026, the classic epics grid will be designated with end-of-support (EOS) status. After that point, no new features will be added and non-critical defects will no longer be filed by our support and development teams.

The classic epics grid page will remain fully accessible prior to and after the designation of EOS status. We do not currently plan to remove access to the page in the foreseeable future. Any changes to the status of the page will be communicated here in future release notes.

To take advantage of the improved functionality, opt in to make the new epics grid page your primary experience for working with epics.

Enhancements and features

Terminology change for objective categories

We’ve updated the values in the Category field of objectives to resolve a display mismatch and align with updated terminology.

The former Critical Path value has been updated to display as Committed, and Stretch goal has been updated to Uncommitted in all panels, pages, and reports.

Existing objectives keep their category assignments, and the way each category is counted in reports has not changed. Integrations and scripts that use the Jira Align REST API are also unaffected.

The new themes grid page graduates from beta

The updated themes grid page is now generally available (GA) for cloud environments. This modernized experience offers more usable ways to find and manage themes, bringing it into alignment with our updated epics, features, and capabilities grids.

To use the new page, switch on the Portfolio > Themes (New) system role permission toggle. For on-premise environments, we expect to release the new themes grid page in version 11.30.

As part of the graduation to GA, we’ve made additional enhancements to the page:

• Export themes: Export the themes that match your current search and filters. You can also include child work items, acceptance criteria, and rich-text formatting.
• Delete multiple themes: Select and delete up to 10 themes at once. Select the check box in each theme row you want to delete, then select the Delete option from the More actions menu.
  • Note: Your role must have the Delete Agile Objects or Manage Agile Objects system role permission enabled in addition to the Themes > Delete permission.
  • Deleted themes can’t be recovered.
• Work with more theme data: Add Portfolio Ask and Milestones as columns and filters, and sort themes by Portfolio Ask.

Roadmaps: group work by theme

You can now group items by theme on epic, capability, and feature roadmaps. Use the new Theme option in the Group by view setting to see how work contributes to each theme and scan related items together.

Roadmaps and grids: display only enabled fields

Column and filter selectors on roadmaps and the themes, epics, capabilities, and features grid pages now respect the portfolio's Details Panel Settings. When a field is disabled for the selected portfolio, it no longer displays as a column or filter option.

Roadmaps: respect portfolio-specific progress settings

Roadmap progress bars now respect the Progress Bar Status platform setting for the selected portfolio, so they measure completion by story points or completed item count as configured. Previously, roadmaps used the global platform setting even when a portfolio override was configured.

Dependency maps: see incoming dependencies across portfolios

Teams and programs can now view dependencies that target them, even when the requesting work is in another portfolio.

Switch on the new Show incoming toggle at the top of the dependency maps page to display these dependencies with your existing results on the Wheel, Grid, Analytics, and Incremental Status views. Each view remembers the toggle’s setting independently.

Incoming dependencies will display when associated with the selected program increment’s date range. Jira Align uses the dependency’s need-by date to position it, or the committed sprint end date when no delivery date is set. Dependencies without either date remain hidden.

Leave Show incoming turned off to keep the current behavior on the page.

Accessibility: improved navigation, contrast, and form guidance

We’ve made 28 accessibility improvements across the home, objectives, OKR hub, and program room pages. These updates make Jira Align easier to understand and operate for people who use screen readers, navigate by keyboard, or need improved visual contrast and form guidance.

• Screen reader support: Improved page titles, heading structures, labels, roles, and control states, and prevented layout tables from being announced unnecessarily.
• Keyboard navigation: Made buttons keyboard accessible and improved focus behavior when opening and closing dialogs.
• Visual clarity: Improved color contrast for text, images, and form controls, and ensured links are not identified by color alone.
• Form guidance: Added clearer instructions for required fields and more descriptive labels for buttons and form controls.

Backlogs: keep ranks accurate after imported scope changes

Jira Align now resets affected backlog ranks when an import changes a work item’s program or program increment.

This prevents stale or historical ranks from reappearing and brings imported changes in line with changes made through backlogs, details panels, API commands, and mass updates. Each rank reset triggered by an import is recorded in the work item’s audit log.

Epics grid: view full values during inline edits

Fields that support inline editing now display tooltips when a value is too long to display in the editor cell. Hover over lengthy values when editing to see the full name.

Bug fixes

We’ve corrected the following bugs that were discovered while investigating related issues, building new enhancements, and performing maintenance:

• Story and feature grids: HTML tags were displayed in Custom Text Area field values.
• Epics and features grids: The Created Date filter incorrectly included a No value option.
• Epics grid: Deep links did not retain the Capitalized column filter.
• Capabilities grid: Exports did not respect the selected Strategic Horizon filter.
• Capabilities grid: Exports did not respect the selected Quadrant filter.
• Features grid: The Notes modal did not display a title, and saved notes could not be cleared from the modal.
• Features grid: Users with access to a feature through an additional program could not edit notes, and the inline Notes modal did not match other modal layouts.
• Features grid: The Teams column displayed values in a tooltip instead of the pop-up used by other multi-select columns.
• Grid pages: The starred-page icon changed from yellow to white when opening a work item.
• Grid pages: Date range filters could return incorrect results after the page was refreshed.
• Roadmaps: Setting the same start and target completion dates for a theme returned an error.
• Roadmaps: The Program (PI) Rank sort by option was reset when switching between epic, capability, and feature work items.
• Roadmaps: The Color by menu displayed Health instead of the Status (Health) terminology used elsewhere.
• Dependencies: The Notify field could display duplicate users in search results.
• Dependencies: Updating a dependency could create duplicate audit-log records for tag changes.
• OKR slide-out: Required-field guidance remained visible after an OKR was created.
• Kanban Board: The Quick Load Cards option was unavailable to super admins and users with the required permissions.
• Navigation: Solutions in the left navigation were not listed alphabetically.
• Teams: A team rename could be lost when saving failed because of a duplicate sprint prefix.
• Objective History: Newly created milestones and changes to assigned work items were missing from the milestone audit log.
• Program increment slide-out: Audit records created after updating a program increment description did not use the configured platform terminology.
• Sprint slide-out: Burn Hours, Defect Hours, and Regression Hours values entered during sprint creation were not recorded in the audit log.
• Sprint slide-out: Audit records for sprint field changes did not use the configured platform terminology.
• Sprint slide-out: Audit records for subscribe and unsubscribe actions did not use the configured platform terminology.
• Azure DevOps connector: Users with long email addresses could not be created in Jira Align during synchronization.

• API: Additional programs submitted through the Epic API were not saved.