Release Notes for 10.108.X


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

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

Enhancements and Features

These features for 10.108 were released to environments on the continuous release track on June 3, 2022, in version 10.108.0. The features will then be released to environments on the bundled release track on June 17, 2022, in version 10.108.2:

Hourly Accepted Spend

Accepted Spend for all work items can now be calculated using task hours logged on accepted stories, in addition to the existing functionality for calculating by effort points. If your team enters task time in a Jira Software project synced to Align via the connector, these hours can now be used for calculations. We also support task time synced from Jira that was logged through the Tempo Timesheets app.

Whether a story’s Accepted Spend is calculated by points or by hours is up to the team. Each team can configure their choice by selecting Hours or Points in the Track By field on the team's Details panel. Within a program or portfolio, there can be some teams tracking by points while others will track by hours, to generate a dollar value that can be summed across stories, then rolled up the work item hierarchy.

When a team chooses to track by hours, Accepted Spend is calculated for a story as:

(Sum of hours logged on child tasks) * (Weighted Cost Rate)


Weighted Cost Rate is a new value that represents the average cost per team member that contributed to a story. This allows members of the same team who report to different cost centers to be accounted for accurately. Weighted Cost Rate is calculated for each accepted story by summing the following from each team member that logged time:

((User’s hours logged on child tasks) / (Total team hours logged on child tasks) * 100) * (Team member’s Cost Center Rate or PI Blended Rate)

Detailed examples (click to expand)

For both scenarios, Team A has 3 team members that worked on an accepted story’s child tasks. The team's Track By setting is set to Hours.

Cost Center Rate

The portfolio the team belongs to is configured to use Cost Center through the Admin > Platform > Portfolio > Costing Method setting.

Each team member belongs to a different cost center as they have different roles and hourly rates:

  • User A - Developer: $80
  • User B - Tester: $70
  • User C - Documentation: $60

Each team member logs the following hours on the story’s child tasks during the course of a sprint:

  • User A: 12 hrs
  • User B: 5 hrs
  • User C: 3 hrs
  • Total time spent: 20 hrs

First, we calculate Weighted Cost Rate:

(User A 12 hrs) / (20 hrs) * 100 = 60% contribution. 60% * $80 = $48
(User B 5 hrs) / (20 hrs) * 100 = 25% contribution. 25% * $70 = $17.50
(User C 3 hrs) / (20 hrs) * 100 = 15% contribution. 15% * $60 = $9

$48 + $17.50 + $9 = $74.50

Next, Align uses the Weighted Cost Rate to determine hourly Accepted Spend:

Total of 20hrs * $74.50 = $1,490

PI Blended Rate

The portfolio the team belongs to is configured to use Blended Rate through the Admin > Platform > Portfolio > Costing Method setting.

Each team member logs the following hours on the story’s child tasks during the course of a sprint:

  • User A: 6 hrs
  • User B: 11 hrs
  • User C: 8 hrs
  • Total time spent: 25 hrs

Weighted Cost Rate is equal to the value entered in the Blended Rate field of the Details panel for the program increment that the sprint belongs to. Because this value is the same for all team members, only one step is needed in the calculation:

PI Blended Rate: $85

Total of 25 hrs * $85 = $2,125

There are a few other behavior changes to consider that support this calculation:

  • As with point-based calculations, a baseline (storage) mechanism applies:

    • At the end of every sprint, Jira Align baselines all members assigned to the sprint and their cost rate (PI Blended Rate or Cost Center Rate).
    • For Kanban teams, membership and cost rates are baselined at the end of each anchor sprint.
    • The number of hours logged for a story is not baselined. Hours are always calculated live. This means that if a user records time on a task after a sprint ends, the new total hours logged will be multiplied by Weighted Cost Rate to recalculate Accepted Spend.
  • If a user that does not belong to a team logs hours for a task, they are added as a member of the team and sprint with 0% allocation. This happens for both hours entered directly in Jira Align and for any hours synced from Jira Software through the connector (when the Allow Jira to add users to team if they belong to an issue setting is enabled).
  • If a story is synced with Jira Software through the connector, hours cannot be logged for child tasks inside of Jira Align. Menus in Jira Align to enter task hours will not be available from the story’s details panel. Time must be recorded in Jira.
  • New teams created in Jira Align or through the Jira Software connector will have the Track By field set to Points by default.
  • The Direct Task Time Entry and Report Hours for Precise Day dropdowns have been removed from global and portfolio-specific settings, as they are no longer used by Jira Align.

Azure DevOps connector: Automatic team assignment

To support hourly Accepted Spend values mentioned above, users associated with work items syncing between Azure DevOps and Jira Align will automatically be added to the team assigned to the work item.

In the 10.109.0 release, we’ll automatically add users to the appropriate sprints and set their allocations.

API 2.0: Financial endpoints

We’ve added the following financial values to our API 2.0:

Values that support GET:

  • Team Spend per Point
  • Normalized Team Spend per Point
  • Program Spend per Point
  • Program Spend per Point by Anchor

Values that support POST:

  • Epic Accepted Spend
  • Capability Accepted Spend
  • Theme Accepted Spend
  • Feature Accepted Spend
  • Release Accepted Spend
  • Epic Estimated Spend
  • Capability Estimated Spend
  • Theme Estimated Spend
  • Feature Estimated Spend
  • Release Estimated Spend
  • Epic Forecasted Spend
  • Capability Forecasted Spend

API 2.0: Links support

You may now perform POST, PUT, and PATCH operations against the Links section found within Details panels for themes and objectives.

Completed removal of operational process flows

In version 10.107.0, we began removing operational process flows and operational process steps from Jira Align. Now, all mentions of this functionality have been removed from Details panels settings, administration settings, process flow pages, page filters, and reports.

Portfolio Room sorting

We’ve added the ability to sort most columns to the grid of epics and stand-alone features found inside the Financials, Resources, and Execution views of the Portfolio Room. For each view, the default sorting will be the ID column in descending order (newest items first). Select a column name to sort the grid.

Columns that support sort:


  • ID
  • Title
  • Owner
  • Budget
  • Program Increment
  • Capitalized

Resources and Execution

  • ID
  • Title
  • Progress
  • Story Points
  • Total PI Estimate
  • Capitalized

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-2131 Story title allows 300 characters in Jira Align but Jira allows only 255 10.108.0
JIRAALIGN-3213 ADO Connector: Default Sync User is a required field, however, documentation implies it can be left unassigned 10.108.0
JIRAALIGN-3219 ADO Connector: Log date filter searching using US date format 10.108.0
JIRAALIGN-3333 ADO Connector: HTML format in Description field is not displayed correctly on Epic Estimation screen 10.108.0
JIRAALIGN-3337 Backlog: Tag colors are not consistent if there are more than 100 items 10.108.0
JIRAALIGN-3963 Story Progress Bar for an accepted story with all tasks done shows 0% when all tasks have 0 hours logged 10.108.0
JIRAALIGN-4083 Dependency between 2 kanban teams fails to display Accept/Decline buttons 10.108.0
JIRAALIGN-4134 ADO Connector: Acceptance Criteria sync generating warning messages 10.108.0
JIRAALIGN-4150 Irrelevant error message while wrong data type was passed while running PUT request on program increments 10.108.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.