Release notes for 10.112.X


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

Enhancements and Features

These features for 10.112 were released to environments on the continuous release track on September 23, 2022, in version 10.112.0. The features will then be released to environments on the bundled release track on October 7, 2022, in version 10.112.2:

Removal of Awards

As previously announced, we’ve removed the Awards / Shout-Outs functionality from Jira Align. Awards was a seldom-used feature that allowed you to create custom badges and point values that displayed on a recipient’s profile page.

Pages removed include:

  • Awards / Shout-Outs main page
  • Shout-Out Awards list page
  • Awards report

Note: For a short time, you may still see references to previously-granted awards on a user’s profile page.

If you attempt to visit these locations through a previously-saved link, bookmark, or Favorites entry in Jira Align’s navigation, you’ll be redirected to a new page that informs you the functionality has been removed. Select the Learn more link from the page to see more info about recently removed functionality, as well as instructions on how to clear old entries from Favorites.

Jira Connector: T-shirt size mapping

We’ve added a new mapping settings window to the Jira Connector settings. This new feature provides you with a way to match up entries in the custom field you use for t-shirt sizes in Jira with t-shirt size names in Jira Align. Previously, values needed to match exactly in both systems for the fields to sync.

Jira_T_Shirt_Setup.png

Find the settings window by navigating to Admin > Jira Settings > Jira Setup and then select the Configure link found next to the T-Shirt field.

Jira Connector: sprint creation

We’ve added more fields that are set on a Jira Align team sprint when it is created by the Jira connector:

  • Goal: the same as your sprint goal in Jira
  • Region: set from the team Region
  • Type: set from the Program Increment sync sprint Type (standard sprint or innovation & planning sprint)

Related to the sprint type, we also fixed an issue where the connector was always creating standard team sprints, even if the program increment sync sprint was innovation & planning. Now, the connector will properly create innovation & planning team sprints.

Jira Connector: Jira Project toggle on Details Panel Settings

We’ve added a Jira Project toggle to the defect work item type’s Details Panel Settings page to be consistent with the logic for features and stories. This setting is always switched on for work items in portfolios whose programs are integrated with Jira.

Also, we have removed the Make selection of Jira projects mandatory when creating items setting from the Jira setup page. The Details Panel Settings page has become the only place to choose whether the Jira Project field should be required for your work items in integrated programs. If the Jira setup setting was on (making the Jira project field required), your portfolio settings were automatically updated to keep the field required.

Related to our Jira Project field updates, you can now filter the feature, story, and defect grid by the Jira Project and view it as a column in the feature, story, and defect grid.

Features now on by default

The following list of functionality previously required enablement by our support or services teams during the initial configuration of Jira Align. This functionality is now permanently enabled and no longer requires manual changes.

  • Email log: In the administration module, admins can view a log of emails sent by Jira Align.

  • View Team Room Long Term Metrics by story points: Allows users to view the Long Term Metrics (program increment burnup charts) report by story points or hours.
    With it enabled, we use a different stored procedure to calculate the release burn-up. This new stored procedure (4 years old) has a daily plot for burn-up points, while the old one had weekly plots for burn-up points.

  • Link to roadmap toggle: Just an old, behind-the-scenes toggle that we needed to get rid of. This change has no impact on users, but we wanted to call it out for our partners who assist in configuring new sites.

  • Support link: Adds a link to Jira Align help and support in the user profile menu.

  • Additional columns available in the backlog: Users can select a parent team rank as a column shown in the backlog (e.g. the portfolio rank of items when viewing the program backlog).

  • Hide stand-alone features from backlog setting: Displays a setting to hide stand-alone features from the epic backlog. Find this setting in platform settings underneath Program.

  • Assessment emails: Assessments are tools that can be used to measure team readiness, health, improvement, progress, or any other facet of Agile, such as maturity. This toggle controlled whether emails would be sent to users to take the assessment.

  • Ideation: Gather ideas or change requests from external users (registered users, but without Jira Align licenses) or internal users (with Jira Align licenses), and allow users to refine and vote upon them. Then, teams can shelve the idea or easily convert them to a Jira Align work item.

  • View features not associated with a team (via a story assignment) on the Program Board.

  • Funding Plan report: This report provides a real-time financial view to a subset of the organization, to enable tracking against its allocated funding levels.

  • Group items on roadmaps: Group items in the Themes, Epics, Capabilities, or Features roadmap views by fields such as owner, primary program, state, and more.

  • View capabilities on Release Vehicle Roadmap.

  • Map Jira statuses to Jira Align process steps with the Jira connector: Allows admins to map Jira statuses to Jira Align process steps instead of states. Process steps are great to use when wanting to customize Align states or simply replicate your Jira workflow in Jira Align.

  • Daily meeting performance: In the daily standup meeting, the What User's working on and Stories owned by User sections are replaced with one Stories section. The burndown chart also only loads once during the meeting to increase performance.

API 2.0: Risks

We expanded the capabilities of our risks endpoints. Custom fields are now supported in all methods (e.g. GET, POST, PUT/PATCH), an /{id}/editmeta endpoint was added so that developers can get programmatic access to property metadata, and dynamic validation was added so that the API enforces the same required fields as defined in your Details panels settings.

API 2.0: Error responses

Previously, we returned a 401 "unauthorized" error when a user did not have proper permissions to perform the API call (e.g. the user does not have permissions to edit features). Now, we’re returning a 403 "forbidden" error to help differentiate the two types of errors.

Coming in 10.112.2: New objectives tree

Jira Align is updating our objective experience with a new and improved visualization of the Objectives Tree. Starting in version 10.112.2 on October 7, new customers will be able to try out the new experience. For existing customers, contact your Solutions Architect or Support to turn on this new feature in your instance.

Once on, you’ll see the new Objectives Tree by default, but will be able to switch between the legacy (current) and new experience. Later, we will deprecate the current experience.

The new experience rethinks the visual representation for strategic goals, objectives, and key results based on your actual goals and needs. Get clearer guidance on what's going well, what needs help, and what's off the rails from a single screen. Or, drill into additional details if needed.

New_objectives_tree.png

Defect Fixes

The list of defect fixes will be updated to reflect changes in weekly maintenance releases. You can see the contents of individual maintenance releases in the Supplemental Release Notes section.

Key Summary Release Version
JIRAALIGN-1282 Jira Connector - IP Sprints are treated the same as regular Sprints 10.112.0
JIRAALIGN-2257 Details Panels Settings page is missing Jira Project field for Defect work item type 10.112.0
JIRAALIGN-3174 Jira Management -> Jira Sprints -> View Logs - Sprint names cutoff 10.112.0
JIRAALIGN-3452 Objective and Key Result OKR: An Archived PI can be selected to be linked to an OKR 10.112.0
JIRAALIGN-3493 Date format changes to US when creating objectives of any tier on Chrome browser 10.112.0
JIRAALIGN-3574 Jira Management Yellow Warning Message doesn't show the real error root cause 10.112.0
JIRAALIGN-3657 Points Planned vs Points Accepted report has "vs." in the left Menu bar 10.112.0
JIRAALIGN-3738 Roadmap: Number of Stories are not showing 10.112.0
JIRAALIGN-3986 JIRA Connector: Incorrect tooltip for the Initial Sprint Start Date option 10.112.0
JIRAALIGN-4077 Quick Select on Program Room throws an error "Not all shared filters could be applied to the page view." 10.112.0
JIRAALIGN-4092 Epics: Target Date is not saved on table tblAgileSuccessMetric when setting the outcome on a Epic 10.112.0
JIRAALIGN-4095 Forecast report hides program names if no team is assigned to the program 10.112.0
JIRAALIGN-4100 Ideation - UI defect, Internal Contributors and Admins combo picker has invisible HTML elements right beside them. 10.112.0
JIRAALIGN-4121 Jira Management > Empty Team gets created when a new board is added under Jira Management but 'Jira Align Team' field is left blank 10.112.0
JIRAALIGN-4157 Jira Connector - Shared Feature does not reflect correct project mapping when issue is moved in Jira 10.112.0
JIRAALIGN-4218 Jira User Data Pull: SSO Id is indicated instead of External Id on the user audit logs. 10.112.0
JIRAALIGN-4240 Pasting text into Business Model Canvas Cards gives character count error 10.112.0
JIRAALIGN-4286 Ideation: No Password Policy Enforced for External Users Registration 10.112.0
JIRAALIGN-4312 Epic Backlog: Changing Epic's rank creates audit log entries for all Epics in backlog even if that item's rank didn't actually change 10.112.0
JIRAALIGN-4320 Scrum to Scrum team sending the proposed date on Dependency results in error upon the attempt to accept the proposed time 10.112.0
JIRAALIGN-4327 Epic: when copying an Epic with children, Stories that are synced to Jira are associated with the original Feature 10.112.0
JIRAALIGN-4348 Jira Connector: 503 error on Jira Cloud produces confusing error 10.112.0
JIRAALIGN-4365 The fields 'Needed by' and 'Committed by' are not showing up in dependency Audit Log 10.112.0
JIRAALIGN-4379 API 2.0 : Objectives : Inaccurate obsolescence message 10.112.0
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.