Release Notes for 10.75


The old navigation will be removed from Jira Align in early 2024.
Learn more about the upcoming changes

End of Support for Internet Explorer 11

To allow us to continue to take advantage of modern web standards to deliver improved functionality and the best possible user experience across all of our products, we have decided to end support for Internet Explorer 11 (IE11). End of support means we will not fix bugs that are specific to IE11, and will begin to introduce features that aren't compatible with this browser.

For cloud versions of Jira Align, support will end on September 26, 2020. For the on-premise version of Jira Align, support will end on September 30, 2020.

In preparation for the end of support dates, we recommend switching to one of our supported browsers, such as Google Chrome, Microsoft Edge, Mozilla Firefox, or Safari.

Please see our Community article for more information or to ask any questions.

Enhancements and Features

Shareable views for grids

Yep, you heard that right! Now you can filter a grid view and share it with your team. By either copying the URL or using the new Share button in the upper-right corner of a work item grid, you can share your view with others, and if they’d like to, they can even save the filter as their own to use it again later.

Configuration bar filtering by product and organization structure on work item grids

The Stories, Features, and Epics pages now respect filtering by product and organization structures in the Configuration bar.

If the grid is filtered by organization structure, all work items display where the owner/assignee user is part of the selected structure or any level below.

If the grid is filtered by product:

  • On the Features page, the grid displays features that are directly assigned to the selected product, or assigned to products at lower levels of the selected product’s product hierarchy.
  • On the Stories page, the grid displays stories whose parent features are directly assigned to the selected product, or assigned to products at lower levels of the selected product’s product hierarchy.
  • On the Epics page, the grid displays epics whose child features are directly assigned to the selected product, or assigned to products at lower levels of the selected product’s product hierarchy.

Performance: Roadmaps dropdown replacements

To load your roadmap filters more quickly, we updated how you apply filters when filtering by theme, epic, capabilities, features, users, products, organizations, and tags. After selecting one of these filters, enter text in a search field to see a list of the top 20 most relevant items. We also applied these changes to the list of customers in the Briefing dropdown menu.

Performance: Work item list on lean use cases

For better user experience with a long list in work item-based dropdowns, we changed the dropdown selection method to loading list by portions for the lists of epics, capabilities, and features on the lean use case slide-out.

API 2.0: Create acceptance criteria on stories

You can now create acceptance criteria using the POST method on stories. Updates and acceptance criteria on other work items will be supported in future releases. When creating acceptance criteria on a story, the story’s last modified date are updated and the changes are added to the audit log.

API 2.0: Create acceptance criteria on capabilities

You can now update capabilities using the PATCH and PUT methods.

API 2.0: Create key results on objectives

You can now create key results using the POST method on objectives. Updates will be supported in a future release.

Usability improvements to the Azure DevOps connector logs

We added new columns to the Azure DevOps connector logs to improve the ability to find and address sync issues. These include Level (to differentiate between errors impeding a work item sync and warnings that may impact a specific field), Item Type, Jira Align IDs, and Azure DevOps IDs. In addition, searching and filtering were enhanced on all applicable columns.

Average Velocity and Override Velocity fields on sprints

We updated the following fields on the Sprint Details panel:

  • Average Velocity: We changed this field to a read-only field. It displays the average velocity over the last five completed sprints.
  • Override Velocity: A new field! If you expect a team’s velocity in an individual sprint will be much higher or lower than average, use this field to reflect the expected velocity for planning purposes. This number will display as the Average Velocity on the Backlog and other pages until the sprint is completed. Using this field does not affect the information displayed in the Average Velocity field.

Work in Process Lean Metrics supports capabilities

The Work in Process Lean Metric charts now provide information on capabilities.
Note that there are a series of calculation defects currently impacting these charts. We plan to fix these in the 10.76 release.

Defect Fixes

JIRAALIGN-1059 Users cannot add columns to the Epic Backlog
JIRAALIGN-1662 Save button doesn’t display in the Override Velocity modal when more than three programs are selected in the Configuration bar
JIRAALIGN-1518 Feature and Capability Backlog display duplicate work items when a solution is selected in the Configuration bar
JIRAALIGN-896 Users cannot rank epics after expanding a theme on the Theme Backlog
JIRAALIGN-1743 The column name for Developmental Step (‘Development Step’) is not consistent with the field name
JIRAALIGN-1739 Users cannot estimate defects when only the Points, Hours, or Remaining(hr) field is turned on in Page Config
JIRAALIGN-1754 Changes to feature assignment are not captured in the dependency audit log

When a feature has been split and the program increment is set to Unassigned Backlog, the child stories don’t change PI to match

JIRAALIGN-1499 When creating a feature or capability, the list of PIs is not limited to the list of the PIs assigned on its parent work item
JIRAALIGN-1063 A feature’s team assignment is not updated when the feature’s program assignment is changed
JIRAALIGN-1745 Risks created from a feature do not inherit the feature’s PI

Filters and sort options are misaligned in ideation portals

JIRAALIGN-1731 Feature associations can’t be removed from ideas
Jira Connector  
Syncing a feature with quotation marks in its name causes a ‘400 BadRequest Unexpected character’ error
JIRAALIGN-1468 When the Approach field is turned off, features become multi-program features and additional programs are automatically assigned. Users can neither remove the additional program associations nor switch the feature back to a single-program feature.
JIRAALIGN-796 Feature status is not updated in Jira when its Jira Align state is updated via promotion of a child story’s state
JIRAALIGN-1700 Links from Jira to canceled work items lead to a blank page
Kanban Boards  
JIRAALIGN-1583 Submit Reason and Close buttons in the Exceeding Limit modal are unresponsive
Lean Use Cases  

An internal server error occurs when creating or opening a lean use case

JIRAALIGN-1595 Check In button does not match modal functionality
JIRAALIGN-1624 Users cannot enter decimal values as key results
Program Board  
JIRAALIGN-1223 Cross-program/program increment dependencies from Kanban to Agile teams don’t display on the Agile team’s Program Board
JIRAALIGN-1708 Users cannot return to the Program Board using a bookmarked link
JIRAALIGN-1759 Multi-program features display multiple times on the Program Board
JIRAALIGN-564 Features assigned to teams from the feature’s additional programs do not display
JIRAALIGN-1539 The Scope Change Report does not display information on multi-program features
JIRAALIGN-1503 On the Status Reports, State bar design does not match other location in Jira Align and the Status indicators fill from right to left
JIRAALIGN-1508 When closing the Risk or Dependency Details panel on the Program Tracking report, the page reloads, even when no changes have been made
JIRAALIGN-1656 When the custom terminology for ‘feature’ is changed to include parentheses, the parentheses do not display on the Investment Report
JIRAALIGN-1347 The Work In Process by State report does not support capabilities
JIRAALIGN-1659 Efficiency, Throughput, and Cycle Time statistics do not display on the Work in Process by Value Stream report, even when Stats are switched on
JIRAALIGN-1645 On the Program Tracking report, action items are not filtered by program when a program is selected in the Configuration bar
JIRAALIGN-1485 The Scope Change Report only displays multi-program features when a portfolio contains a mix of single- and multi-program features
JIRAALIGN-1502 The Status Reports page takes minutes to load or fails to load

The Cycle Time graphs in the Work In Process by State report do not display correct data


The Lead Time chart in the Work in Process by State report uses incorrect calculations for epics

JIRAALIGN-1545 The Release Vehicle roadmap does not filter by product when one is selected in the Configuration bar and archived release vehicles display in the report
JIRAALIGN-1675 ‘Looks like we couldn't find any data’ message displays when loading roadmaps with large amounts of data
JIRAALIGN-1484 The bar for a feature shifts by one day when clicked

The list of tags to filter by times out or takes over 20 seconds to load


The Feature by Epic option displays when viewing the roadmap for a program with capabilities


Users cannot apply Tags filter to the story grid


Users can assign stories to inactive Agile teams

 Work Tree  
JIRAALIGN-1686 The dropdown menu for snapshot selection does not have a label
JIRAALIGN-1246 Orphan story counts don’t match in the Backlog and Program Room
JIRAALIGN-1530 Average Team Velocity counts don’t match in the Capacity Planning report, Team Room, & Backlog
JIRAALIGN-1609 User icons do not display initials when user data has been migrated from an on-premise Jira Align instance to a Cloud instance
JIRAALIGN-1668 In the Details Panel Settings, selecting Capability as the work item level to edit resets the portfolio selection
JIRAALIGN-1669  In the Details Panel Settings, portfolio and work item selections disappear after the settings are saved
JIRAALIGN-722 Users with read-only access are able to add attachments to all work items and then cannot delete them
JIRAALIGN-1713 Users cannot access the Scheduled Email Log
JIRAALIGN-1638 Updates to the platform terminology save without clicking Update Terminology and no confirmation message displays
JIRAALIGN-1615 API 2.0 endpoints do not accept ordering by date fields
JIRAALIGN-1706 Toaster messaging on work item Details panels does not contain consistent capitalization when a user updates platform terminology
JIRAALIGN-541 Large data searches result In ‘Whoops’ errors on the Change Logs
Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.