The Jira Align support guide provides an overview of the various help resources available for Jira Align, as well as guidelines for creating and monitoring support tickets, feature requests, and test instance refresh requests. We recommend reading this guide to assist you in creating better cases and getting issues resolved as quickly as possible.

Check it out in the Atlassian Community here.

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.

Below is our upcoming release schedule. Sandbox and production environments will be unavailable during our maintenance window, which starts at 11:00PM EST on the day listed below and ends at 2:00AM EST on the following day.

Release tracks

Production environments are set to use the bundled release track, while sandbox environments use the continuous track. We recommend using this default setup for your environments, as it allows you to test new features released in a .0 feature release for two weeks in your sandbox environment. Those changes will then deploy to your production environment in a .1 maintenance release. 

Jira Align's Enterprise Insights (EI) version 11.27 was deployed to environments on the continuous release track on July 17, 2026. It will then be deployed to environments on the bundled release track on July 31, 2026.

Release highlights

There are no functional changes or bug fixes included in version 11.27. The Enterprise Insights schema remains on version 11.22.

Below is our upcoming release schedule for Enterprise Insights (EI). Sandbox and production environments will be unavailable during our maintenance window, which starts at 11:00PM EST on the day listed below and ends at 2:00AM EST on the following day.

See the Release calendar article for the schedule of releases for the Jira Align platform. 

The installation and upgrade process for self-hosted Enterprise Insights is changing with version 11.23. Read on to understand what's new and what steps you need to take.

Enterprise Insights 11.23 contains a reliability and flexibility update for the self-hosted installer. It introduces answer file support for repeatable deployments, comprehensive pre-flight validation, and expanded SQL Server connectivity options.

Benefits of the change

Installing and upgrading Enterprise Insights in self-hosted environments has historically required careful manual input and could surface errors late in the process. This release addresses that by:

• Catching problems before they start: credentials, version compatibility, and database readiness are all validated before any changes are made
• Enabling repeatable, unattended deployments: a new answer file lets you configure once and reuse across environments and upgrades
• Supporting more deployment topologies: remote SQL Server, non-default ports, and self-signed certificates now work without manual script modifications
• Making upgrades seamless: existing ETL jobs are detected and handled automatically, eliminating common upgrade errors

All changes are fully backward compatible. Existing installations using default settings will continue to work without modification.

What's included

Answer file for unattended deployments

You can now pre-configure all installer inputs in a single answer file and run installations without interactive prompts. A documented template (Install.Answers.psd1) is included in the installer package, organized into clear sections (Data Warehouse, SSIS Catalog, SQL Admin, ETL Job, and Jira Align connection) with inline comments explaining each setting.

Key benefits:

• Eliminate manual entry: no more typing 15+ values at each install or upgrade
• Reduce errors: pre-validated configuration catches typos and missing values before deployment starts
• Enable automation: fully scriptable for CI/CD pipelines and scheduled upgrades
• Document your environment: the answer file serves as a living record of your deployment configuration
• Hybrid mode: leave any value blank to be prompted interactively; pre-fill the rest

To get started, copy the included template, fill in your environment values, and pass it to the installer. For fully unattended operation, add the -Force flag to skip confirmation prompts while retaining all safety checks. See the Self-Hosted Enterprise Insights Guide for detailed instructions.

Security: Answer files containing credentials should be stored securely and excluded from source control. See the template comments for guidance.

Pre-flight validation

The installer now performs a comprehensive set of checks before making any changes to your environment:

• Credential verification: all database connections are tested up front, so you will know immediately if a password or server name is wrong
• Version compatibility: Enterprise Insights and Jira Align versions are compared, with a warning on mismatch to prevent accidental misalignment
• Database readiness: active connections, open transactions, and database state are checked to prevent deployment failures
• Existing ETL job detection: if a job with the same name already exists, the installer shows its current status and safely handles the replacement

This means configuration problems surface immediately, not partway through a deployment.

Flexible SQL Server connectivity

The installer now supports a wider range of SQL Server deployment topologies:

• Remote SQL Server: Data Warehouse, SSIS catalog, and Jira Align databases can each be on separate servers
• Non-default ports: standard server,port format is now supported across all connections
• Self-signed certificates: a single configuration option enables certificate trust across all SQL connections, eliminating the need to manually edit the script

Additional improvements

• Smoother upgrades: upgrading with the same ETL job name now works seamlessly. The installer detects the existing job, displays its status, and handles the replacement automatically, including safely stopping a running job before deployment begins.
• Better error reporting: when an error occurs, the installer identifies which step failed, provides the specific error with resolution guidance, and reports which steps were not yet executed
• Schema deployment reliability: required deployment files are validated before starting, and failures are detected and reported immediately with log file references
• Updated branding: legacy product references updated to "Enterprise Insights" throughout the installer

Resolved issues

This release addresses several issues reported by customers and identified during testing:

• "MODIFY File Failed. Size is greater than MAXSIZE": the SSISDB file size configuration now checks current file sizes before applying limits, preventing errors when database files have grown beyond the original defaults
• "The specified job already exists" during upgrades: re-running the installer with the same ETL job name no longer fails. The existing job is detected and replaced safely.
• "The certificate chain was issued by an authority that is not trusted": self-signed certificate environments are now supported via a single configuration option, eliminating the need to manually edit the script
• Schema deployment failures not reported: the installer now validates deployment results and halts immediately with a clear error message and log file location if the schema update is unsuccessful
• Installer requires localhost SQL Server: the installer now supports remote SQL Server instances and non-default ports for all connections

Changes to installation and upgrade procedures

The installer package now includes the following files:

For new installations:

No special action required. Follow the Self-Hosted Enterprise Insights Guide included in the installer package. We recommend using the included answer file template for a streamlined experience.

For upgrades from a previous version:

1. Ensure both Install.ps1 and Install.Helpers.ps1 are present in your installer directory. Both files are now required.
2. Run the installer as before. All new settings default to previous behavior.
3. We recommend creating an answer file from the included template (Install.Answers.psd1) to simplify this and future upgrades.

System requirements are unchanged: PowerShell 5.1, Windows Server 2019 or later. Compatibility has been verified with SQL Server 2019.

If you have questions about this change or installing/upgrading Enterprise Insights on-premise, please contact Atlassian Support.

You can subscribe to three Help Center sections to receive notifications the instant release note articles are published:

• Release notes: These articles contain compiled information on a Jira Align version, initially published for the 10.X.0 feature release and updated each additional release through 10.X.3.
• Announcements: These articles contain information about upcoming changes, updates about ongoing issues, or specific guidance outside of our normal release schedule. 
• Enterprise Insights release notes: These articles contain release notes specific to Jira Align Enterprise Insights (EI).

What you need to do

To receive real-time release notes publication notifications, you'll need to create a Help Center account and follow the section or sections you want to receive notifications about. Please note, this will most likely be a different username and password than your Jira Align and Atlassian username and password. 

 To create an account (or reset your password if an account already exists), click the SIGN IN button on the Help Center (see the pink arrow).

Next, click the Sign up link, enter your name and email, and then click the Sign up button. You'll receive an email to finish setting up your account. If you receive a message that says a user has already signed up with the given email, click the Forgot my password link to reset your password.

Once logged in, from the Help Center home page, click the WHAT'S NEW section (bell icon).

Then click the header for the section you want to follow. Finally, click the FOLLOW button and then the New articles link.

That's it! As soon as we publish new release notes, you'll receive an email notification with a link!