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

• Coming soon
• Enhancements and features
• Bug fixes

Coming soon

Upcoming end-of-support (EOS) status and removal for JET app

The JET app for Jira will be designated with end-of-support (EOS) status as of September 17, 2025. We then plan to remove access to the app sometime before December 31, 2025. We’ll provide updates on this timeline in future release notes. This removal is to support Atlassian’s EOS plan for marketplace apps built with Connect.

Enhancements and features

These features for 11.14 were released to environments on the continuous release track on July 18, 2025, in version 11.14.0. The features will be released to environments on the bundled release track on August 1, 2025, in version 11.14.1.

Beta roadmaps: Inline date edits

You can now make edits directly in beginning and ending date fields on the beta roadmaps page. To edit dates on a roadmap, set the Start / Initiation and/or Target Completion fields to display from the Columns menu, then select a roadmap item’s date to open a calendar picker. 

Your selection will be saved instantly, once you leave the field.

Notes:

• Date fields may be named differently in your instance according to custom terminology settings.
• Ending dates must be equal to or later than beginning dates.

Beta roadmaps: Suggested dates

Need some help finding the right entries for empty date fields? You can now quickly fill in missing dates on your roadmap with the new suggested dates feature. To get started, select the Suggested dates button at the top of the page: 

This places you into suggested dates mode, where suggestions display in italics with a plus icon. Striped roadmap item bars are also shown, giving you a visual cue on your timeline. 

Dates are suggested using a roadmap item’s program increments. The start date of the earliest program increment is referenced for blank beginning date fields, and the end date of the latest associated program increment is used for blank ending date fields. 

To use a suggestion, select a cell, and a calendar picker will display with the recommended date highlighted. Select the date to stage the change as an edit to the roadmap item. You can also select a different date. 

The cell will display with a blue highlight in its top-right corner, indicating it is a pending change. After you’ve staged one or more date edits, select the Submit button at the top of the page. 

Select Confirm to save your changes. 

Any suggestions you did not interact with will be ignored, and you can return to suggested dates mode to see them again.

Beta roadmaps: Track progress

Now, you can easily monitor the status of roadmap items as work moves forward, helping you anticipate issues and make timely adjustments. 

To see status at a glance, add the Progress column to your roadmap from the Columns menu. A mini progress bar will display for each roadmap item. The bar will show as filled, depending on the percentage of aligned work.

For objectives, the bar will fill according to completed key results. For work items, the bar will fill using either accepted story points or story counts, depending on the Progress bar status dropdown found inside portfolio settings: 

Select any progress bar to see a detailed card, showing more data about the item's progress.

Specific add and save permissions for epics and capabilities

We’ve introduced separate Add and Save system role permission toggles for epics and capabilities, giving admins more precise control over who can create versus edit high-level work items. Previously, a single toggle governed both actions, making it difficult to restrict creation without also blocking edits. The new options provide more consistency in Jira Align, matching the permissions model for themes, features, and stories.

You can review the new permissions on the far-right side of the rows for epics and capabilities: 

Existing permissions have been migrated so that your users retain current access without interruption. Any user or role that had the old Add/Save permission toggle enabled will have both the new add and save toggles enabled.

Corrected permissions for copying features

As part of our work to provide more consistency with new add and save permissions, we were able to identify and resolve a bug related to features. Previously, the Save permission was required in order to use the Copy function on a feature's details panel. We've updated system logic to validate the correct permission toggle, Add, as a copying creates a new work item.

Jira connector fixes with continuous deployments

Continuous deployments, which allow for quicker resolution and deployment of bug fixes throughout the week, now include changes to the Jira connector. This means that bugs related to the connector can be fixed as soon as a resolution is available, instead of waiting for the next Friday maintenance release window.

New banners in audit logs

To prepare for the upcoming archival of older audit log entries, we've added informational banners to the following pages in Jira Align:

• Main audit log
• Jira connector audit logs
• Work item audit logs
• Feature audit logs accessed from the program board

As previously announced in our product roadmap presentation, we plan to begin archiving audit log entries greater than 13 months old. 

This change will significantly improve the performance of audit logs and other pages inside Jira Align, especially in environments with large amounts of data. While these older audit log entries may not be visible in the UI or API, we will retain these records in our database tables, which you can access through Enterprise Insights. 

We'll provide more details and what version we are targeting for release in the coming weeks.

Bug fixes

This list of resolved bugs will be updated weekly to reflect changes from maintenance and bug fix releases. 

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

11.14.0

• On beta roadmaps, date information displayed when hovering overlapped displayed column data.
• On the drill-down view of the program increment progress report, predicted, pessimistic, optimistic lines were not displaying for themes
• On the program tracking report, the wrong state was displayed when viewing a tool tip for escalations.
• From the program increment progress report, the burn details panel would show a duplicate record inside the End Date column.
• The blank state message found on the status reports page contained a spelling error.
• Audit logs for objectives were not showing changes to scores after adding a key result without baseline or goal values.
• The Tier field on objectives was not displaying correctly when users with view only permissions accessed details panels.
• When adding or removing items from objectives, the Key results and Aligned work items sections of details panels were not updating.
• Unexpected special characters were displayed in audit log entries after modifying an epic's relationship.
• A blank details panel would display when attempting to edit an epic’s process step.
• Team details panels were not rendering correctly when a team was associated with a program with a lengthy name.
• Child items would not reassign correctly after splitting an epic with capabilities enabled.
• Users without edit permissions to features were able to edit acceptance criteria, but unable to save.
• On epic and capability backlogs, the MVP filter was incorrectly displayed as MMF.
• On backlogs, the total items count would not change after moving a theme to another release or the unassigned backlog.
• Custom terminology settings were not respected when viewing discussions for features.
• On the epics grid page, an error would display when attempting to access the Print epic cards option.
• On epic and capability backlogs, an error would display when attempting to drag and drop cards inside kanban views.

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.13 was deployed to environments on the continuous release track on June 20, 2025. It will then be deployed to environments on the bundled release track on July 3, 2025. The following changes are included in version 11.13:

Coming soon

Version 11.14:

• Two new columns, Owner and Requester, will be added to Dependency views.
• A new column, Release Vehicle Description, will be added to Release Vehicle views.

Release highlights

Enhancements and features:

• We removed Design Component rows from the Discussion view.

Bug fixes:

• JIRAALIGN-8270: Platform terminology changes made to feature terms from Jira Align UI weren't updated in the [current_dw].[Agile Object] table.

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. 

We’re excited to announce that continuous deployments have officially arrived with Jira Align version 11.8. This advancement will allow us to deliver critical updates more frequently and efficiently, ensuring that you receive the latest fixes as soon as they are ready.

More fixes, zero downtime

We can now deploy bug fix releases as often as daily, without impacting your workflow. Continuous deployments follow zero downtime deployment (ZDD) standards, so you'll continue to have access to your environment during an update.

What’s included

Currently, continuous deployments focus on resolving bugs that affect the core functionality of Jira Align. In the future, we plan to expand this scope to include connectors and other features, such as Enterprise Insights.

Only bug fixes and other changes to resolve issues will be included in these versions. Features, process improvements, and other planned changes will continue to be provided on our standard release schedule.

Stay informed

To stay informed about the issues resolved in each bug fix release, you can do the following:

For bugs that you’ve reported or impact your environment, watch the issue in our Jira instance, jira.atlassian.com. You’ll receive notifications as we progress on investigating and implementing a fix. Once a fix is tested and committed to a new version, an entry will be made in the Fix Version/s field.

You can view the current version your environment is running on the login screen, or through the About page, accessed from your avatar menu in the upper-right corner of Jira Align.

Additionally, every Friday, we will update the current release notes article with a list of bugs fixed during the week. Look for “Last updated:” at the top of each release notes article and at the top of the bug fixes section to see when additions were last made.

We are committed to continuously improving Jira Align and providing you with the best possible experience. Continuous delivery is a significant step forward in achieving this goal, and we look forward to your feedback as we roll out this new capability.

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

• Main 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.
• Supplemental Release Notes: These articles contain information on individual supplemental releases, published each release from 10.X.1 through 10.X.3.
• Enterprise Insights Release Notes: These articles contain release notes specific to Jira Align Enterprise Insights (EI).

We recommend subscribing to both the Main and Supplemental Release Notes sections to get weekly notifications on the latest Jira Align version.

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!