Release Notes for 10.93

• Enhancements and Features
• Defect Fixes

Enhancements and Features

Improved performance for the WIP by State report

We optimized SQL performance on the WIP by State report to make loading data faster. Previously, the time to load data with over 10,000 stories took 9 minutes. With the new SQL, the same data loads in about 60 miliseconds.

Estimation conversions

For those who recall the updates coming down the pipeline for estimation conversions, the time has come! We simplified the estimation conversions to have one global Member Weeks (MW) → Points field for all three work items.

This change may affect your instance if you’ve entered different values into the member weeks pivot field for different work items. In these cases, Jira Align will use the MW → Points value entered into the field when the work item type dropdown is set to Epic. For example, if your estimation conversion settings currently has “1 MW = 5 story points” configured for epics, but features have “1 MW = 2.5 story points”, all feature estimations will change to use the configured value for epics, meaning their conversions from MW to points will be 5 points, instead of 2.5.

Forecasting

Introducing usability enhancements for forecasting!

Most notably, we overhauled the Plan Capacity modal for Member Week (MW) or Team Week (TW) forecasting. The new design aims to simplify the process of planning for future capacity. This includes moving the program and team sections above the fold of the modal, while buffers and specialists can still be configured towards the bottom of the modal. We also adjusted the columns on the modal so it’s more intuitive to see how current and planned FTEs translate into TW or MW capacity across all teams in a program.

We’ve also updated the calculations for columns displayed in the modal, to make adjusting your capacity prior to entering forecast estimates more clear:

• Planned Capacity (MW): (Planned FTE value x # of weeks in the PI based on the anchor dates)- total buffer
• Planned Capacity (TW): ((Planned FTE value / 6) x # of weeks in the PI based on the anchor dates)- total buffer

• Current FTEs: Calculated based on team member allocations to each child team of the program. For example, if a user has an allocation of 80% on a team, they will count as 0.8 FTE. If they have no allocation, it will default to 1 FTE.

• Planned FTEs: Provides the fieldswhere you can adjust the amount of FTEs that will be available for an upcoming PI. This is useful for accounting for known staff increases or decreases. If the FTEs will not change in the PI you are forecasting for, click the Use Current FTE link at the bottom-right to copy values from Current FTEs.

• Needed Capacity: Sum of forecast estimates already entered on work items associated with the program/team and planned for the selected PI.

  In addition, on the Forecasting page, we’ve re-arranged some of the columns. In particular, the progress bar is now next to the work item name.

Lastly, we’ve updated the header that displays above the columns you use to enter forecast estimates for work items:

• Capacity Remaining = Planned Capacity - Capacity Forecasted
  • Displayed below Capacity Remaining is the total of forecast estimates / total capacity available for the program/team:
    

API Documentation updates

We updated our API documentation to identify properties that are read-only.

Defect Fixes