2024R1.0 - Controlled Release 2

A controlled release will be deployed in order to address the following issues. It will be available on the staging site on Wednesday, May 15th, 2024 and on the production site on Sunday , May 19th, 2024. Individual customer cases will be updated by the support team through the portal.

Note: This page could be updated as new information becomes available.

 

A bug prevented users from saving Metrics with negative values in specific currencies. While the majority of currencies were supported, negative values in certain currencies would cause unexpected errors.

For example, users could save a negative Metric value when the work item's currency was set to United States Dollars (USD):

However, users could not save negative values if the work item's currency was changed to Norwegian Krones (NOK):

An error banner would claim that the Metric could not be saved due to "invalid data":

This bug has been fixed; Metrics with negative values can once again be saved regardless of the work item's currency.

A bug prevented specific users from capturing Baselines for work items. Even when the users had the "Set Baseline Dates" Project permission on the work item, they were still unable to capture Baselines. Only the user with the Project Owner role could successfully capture a Baseline for the work item.

An investigation into the issue found that users were blocked from capturing Baselines when they did not have the "Set Baseline Dates" permission on any of the work item's Descendants. This is not the expected behavior; when a user captures a Baseline for a work item with Descendants, Baselines should be captured for all of the Descendants that the user has the "Set Baseline Dates" permission on. The Descendants that the user does not have this permission on should simply be ignored instead of causing an error.

Note: Capturing a Baseline from the Summary page will automatically capture a Baseline for all of the work item's Descendants as well. If you would like to control which Descendants will also have Baselines captured, you will need to use Project Central.

This bug has been fixed; any user with the "Set Baseline Dates" permission on a work item can once successfully again capture Baselines.

A bug caused numeric Metric values to be displayed in the Arabic alphabet when the Metric's work item used an Arabic currency. For example, if a work item had its currency changed to United Arab Emirates Dirhams (AED), the Metric values would appear in Arabic characters:

Once a user translated the page to English using their web browser, the values were no longer displayed in Arabic characters:

However, this worked contrary to the expected behavior; users should not have to translate their browser pages. Metric values should not appear in Arabic characters by default.

This bug has been fixed; Metrics will once no longer display values in Arabic characters when a work item uses an Arabic currency.