Release notes for 11.27.X

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

• 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.

Beginning with 11.27, you can opt in to make the new epics grid page your primary experience for working with epics.

Enhancements and features

These features for 11.27 were released to environments on the continuous release track on July 17, 2026, in version 11.27.0. The features will be released to environments on the bundled release track on July 31, 2026, in version 11.27.1.

Opt in to make the new epics grid page your default experience

The new epics grid page reached general availability status in version 11.22. Beginning with version 11.27, you can opt in to make it your primary experience. If you prefer, you can keep using the classic epics grid, which remains available as it moves to end-of-support.

• Updated navigation: Once you opt in, primary menu, context sidebar, and workflow entry points route to the new epics grid page. Links in notification emails generated after enrollment will also point to the new page.
• Continued classic grid access: Classic epics grid navigation links are hidden after you opt in, but you can still navigate to the classic grid at any time from the Switch to classic grid option in the More actions menu of the new epics grid page, or by using its direct URL.
  
  • Note: The Switch to classic grid option is a navigation action only, it does not change your default experience or revert your opt-in.
• Role settings permissions: Your existing epic role settings permission toggle settings continue to be respected in the new experience. Once you opt your environment into the new page default, the Portfolio > Epics (NEW) permission toggle becomes read-only and is tied to the original Epics toggle. You’ll no longer need to manage two toggles for access.
  

How to opt in

1. Open an Atlassian support ticket with the title “Opt in to new epics grid default”.
2. In the ticket, confirm that you want the new epics grid page to be your primary experience for working with epics.
3. The support team reviews your request and coordinates enrollment with engineering. If you change your mind, a rollback to the classic grid as default is available.

Continued classic grid presence

There are some links, actions, and other navigation paths that will continue to load the classic epics grid, regardless of opt-in status and upcoming EOS status:

• Links from the Investment vs Spend page.
• Existing links to the classic page, or other direct URLs will continue to load correctly. There will not be redirects to the new page.
• Modal-based views of epics within other panels. For example, search results from the details panel of a risk when associating a related epic.

New setting: disable automatic parent state rollup

Administrators can now control whether a child work item’s state change automatically updates its parent’s state. From platform settings, use the new Automatically update parent state when child work items change option in the General tab to control automatic state rollup.

• When set to Yes: Changes to a child work item’s state, for example moving a story to In Progress, automatically update the state of its parent feature, epic, or capability. If process steps are mapped with states, those will update correctly as well.
• When set to No: Child state changes no longer update parent items. Parent state must be updated manually.
• Default state: This new setting will deploy set to Yes, preserving the existing behavior of Jira Align.

The new capabilities grid page graduates from beta

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

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

• New columns
  • Quadrant
  • Product
• New filters and sorters
  • Quadrant sorter
  • Quadrant filter
  • Product filter
• Import and export support

We’ll continue to expand the modernized grid experience across the capability, feature, and epic levels in future updates.

API: Discussion endpoints for epics, features, and capabilities

We’ve added discussion endpoints for epics, features, and capabilities to the REST API, giving you the ability to integrate work item conversations into your automation and reporting workflows.

• List discussions: Use GET to retrieve all discussions on a specific epic, feature, or capability, including nested replies.
• Create discussions: Use POST to add a new comment or reply to a work item programmatically.
• Delete discussions: Use DELETE to remove a comment and its replies from a work item.

API: Notes endpoints for epics, features, themes, and capabilities

The Notes field, which appears in status reports and as a selectable column in roadmap views, is now available through the REST API for epics, features, themes, and capabilities. It is exposed inline on each work item DTO, following the same pattern already used for tasks and milestones.

• Read: The notes field is returned on both single-item and list GET requests for epics, features, themes, and capabilities.
• Create and update: Set or change content inline through the main POST, PUT, and PATCH endpoints.
  • Content is limited to 2,000 characters.
• Opt in on list endpoints: The field is omitted from list responses by default. Pass ?includeNotes=true to include it.

New epics grid improvements

We've added new columns, an actionable milestones icon, and expanded inline edit support on the new epics grid.

• Capitalized column: A new Capitalized column is available on the new epics grid.
• Actionable milestones icon: Each row's Milestones column now displays an interactive icon. Select the icon to see the details of milestones status associated with the epic.
• Inline edit for more field types: Custom Single Select and Process Step fields now support inline editing on the new epics grid.
• Read-only mode with details panel open: When the epic work item details panel is open, inline editable fields on the epics grid are read-only, preventing editing conflicts.

Name column now draggable

The Name column can now be repositioned on new grid pages with drag-and-drop, so you can place columns like External ID next to ID for easier scanning.

Bug fixes

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

11.27.0

• API: The Stories API returned a 500 error when filtering by DateTime Hour or Minute fields.
• Audit log: Changes to an epic's start or target date made from the new epics grid were not recorded in the audit log with the correct platform terminology.
• Epics grid: Removing a required start or target date via inline edit on the new epics grid showed a generic error message instead of a clear explanation.
• Process column: The tooltip and popup for the Process column showed story points accepted instead of features accepted at the top of the list.
• Epics and features grids: A notification was shown unnecessarily when changing the Custom Room in the left sidebar.
• OKR slideout: Switching between pages in the Aligned Work Items section incorrectly affected pagination state for other work items.
• Dependency grid: Confirmation modals in the Committed by column used incorrect terminology.
• Backlog: The Solution header remained visible on the Program backlog when it should have been hidden.
• Slideouts: Opening a slideout from the Mass Add Kanban board could result in a corrupted slideout being displayed.