Release Notes for 10.62


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

Notice for On-Premise Customers

ASP.NET Core Runtime 3.1.0 required with Jira Align 10.64 (February 19, 2020) release

In preparation for the launch of a new set of Jira Align APIs and to take advantage of new database management tools, Jira Align will require ASP.Net Core Runtime 3.1.0 with the 10.64 release. More information and a link to download can be found here:

Please reach out to Jira Align Support with any questions.

Enhancements and Features

Centralized administration page for field settings and custom fields

For simplified management of field visibility, required fields, and custom fields, we’ve combined the unique Page config links found on work item Details panels into a centralized location, found at Administration > Settings > Details Panels Settings.


To change field settings, first select a portfolio and work item type. You may then enable or disable a field’s active and required states. You can also create custom fields from this menu as before. 

All of your existing field settings have been retained in the new location.

Program increment team membership

We’ve added team membership requirements to the data displayed when viewing the Details panel of a program increment:

  • To view the ID and name of an associated work item, you must be a team member in the work item’s program.
  • If there are associated work items that you do not have access to via program membership, you will see a count of those items.

    Details Panels Settings
  • You must be a team member in the portfolio a program increment is assigned to in order to edit the Portfolio field. 

Roadmap detached instances

We updated the list of detached instances displayed in the View My Instances menu to show the 20 most recent instances you own. 

Jira Connector management improvements

We’ve made multiple improvements to the following Jira connector settings pages:

  • Administration > Jira Settings > Manage Projects
    • The red warning indicator has been replaced with a yellow indicator that is consistent with the indicators found in the Jira Management settings page. The warning will display next to projects with errors returned from API calls. Hovering over the indicator will display details.
    • Buttons on the page have been moved to the top of the table to provide quicker access to logs and integration of new projects.
    • Pagination has been added to the table and is tied to user preferences.
  • Administration > Jira Management > Jira Boards
    • When configuring new boards, required fields now have tooltips so users can easily identify the data they need to input.
    • Pagination has been added to the table of boards and is tied to user preferences.
    • The "No Project Found" error has moved.  This will now indicated by a yellow warning icon on the Jira Boards tab, accompanied by a tooltip.  See below for an example:

  • Administration > Jira Management > Jira Sprints
    • A warning indicator will display when either of the following conditions are met:
      • If multiple Jira sprints are mapped to a single Jira Align sprint. Make sure only one Jira sprint is mapped to a sprint in Jira Align.
      • If Jira Align sprints are not mapped in calendar order.

Defect Fixes by Area


  • We fixed an issue where features could be split indefinitely. Now, features can only be split once.


  • We fixed an issue where users who were assigned roles of Product Owner, Scrum Master, Analyst, or Team Coach for a team were unable to modify the sprint of a story, unless they were added to the team via the Members tab of a sprint’s Details panel.


  • Previously, blocked tasks could set as Done, yet remained blocked. Now, any blocked tasks that are moved to Done will be automatically unblocked.

Test Cases

  • We fixed an issue where some users would experience server timeout errors when attempting to access the Test Cases page.


  • We fixed an issue where users could set the Chat and Stories fields to a Required state, causing errors when attempting to create or save dependencies. The Required toggle for both fields has been disabled in Page config and field settings menus. 


  •  We fixed an issue where email notifications were not triggered when mentioning a user in the discussion of an impediment.


  • We fixed an issue on the Story Backlog page where right-clicking a story and selecting Move to Sprint would not result in any change. Now, stories will be moved to the selected sprint.
  • We fixed an issue where the unassigned backlog section of Backlog pages would not filter correctly when a team was selected in the Configuration bar.


  • We fixed an issue where features and capabilities were not displayed on the Roadmap page when a team with relevant work was selected in the Configuration bar. 

Program Board

  • We fixed an issue where the Unassigned Features toggle setting in the Extra Configs menu of the Program Board was not retained when revisiting the page.

Team Room

  • We fixed an issue where some users would experience server timeout errors when attempting to access reports from the Team Room.

Story Maps

  • We fixed an issue where users with view-only access to Story Maps were able to save changes.


  • We fixed an issue where the total counts of planned stories on Sprint Metrics (M1) and Sprint Coaching reports were not aligned. Now, both report's values are equal and based on the number of stories planned per team per sprint.
  • We fixed an issue on the Feature Forecast report where calculations were being artificially inflated by 100 percentage points.


  • We fixed an issue where user imports required a UID, but would not retain the value after import.


  • We fixed an issue where some external ideation users would not receive an email notification when a comment was added to a subscribed idea.


  • We fixed an issue where accepted work items were erroneously selectable from the Parent field when editing a work item.
  • We’ve updated the error message displayed when attempting to upload an invalid file type to notify the user that the file type is not supported.
  • We fixed an issue where instances that contained duplicate usernames could not tag those users in work item discussions.
  • We’ve enhanced the permissions for survey creation to include roles other than super admin.
  • We fixed an issue with the Jira Align to Jira Align internal connector where sync would fail if Product functionality was enabled.
Was this article helpful?
1 out of 1 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.