2024R1.1 - Resolved Issues

A bug prevented PowerSteering administrators from saving their Dashboard Layouts when one of the Document columns did not contain a column name.

Attempting to save the layout with an empty "Column Name" field would result in an error.

Dashboard Layouts are expected to be saved even if Document column names are not provided.

This bug has been fixed; administrators can once again save their Dashboard Layouts without providing column names for all Document columns.

A bug prevented users from exporting their Dashboards in PowerSteering. Selecting the Export button on the Dashboard page resulted in an "unrecoverable problem".

This bug has been fixed; Dashboard viewers can once again export their Dashboards without issue.

An issue caused Measures to be automatically deleted from certain Dashboard Layouts every few months. An initial investigation into the history logs did not indicate any users who edited the layouts to delete a Measure. Further investigation provided evidence of specific users deleting a Measure from the layout without having permissions to do so.

With this update, PowerSteering has implemented specialized loggers that will target these specific deletions. The root cause of these deletions will be clear once they happen again.

A bug prevented the selected sum amounts from copying over to new Dashboard Layouts that were created by copying an existing one. When users copied a layout, the checked "Summaries" boxes in the "Sum" column would not be copied over automatically. These values are expected to be replicated on new Dashboard Layouts after being copied.

This bug has been fixed; the selected "Sum" values from original Dashboard Layouts will now be reflected in Dashboard Layouts created through copying.

A bug prevented users from updating Descendants in PowerSteering. After navigating to a Summary page of a work item they would like to add the new Descendant to, the Descendants module would display a 500 service error. Users were not able to add any Descendants at this time.

This bug has been fixed; Descendants can once again be added to work items in PowerSteering.

An issue prevented users from selecting every work item on a Financial Review Layout. When users selected the checkbox in the column header, only work items that were on the current page were selected.

Work items that did not fit on the current page would not be selected with the rest. This prevented users from selecting all of the work items in a layout at once, making it difficult to perform a bulk lock/unlock or set all the work items as "Ready for Rollup".

This issue has been fixed; when users select the checkbox in the column header, every work item in the layout will be selected, not just the work items on the current page.

A bug prevented gates from advancing after approval was obtained. On Gated Projects with no Conditions, users would find that the gate would not automatically advance once it was approved. An investigation found that previous gates were being automatically reactivated when users changed the status of the gate. These previous gates would once again require approval, but approval had already been provided so the gate was stuck.

This bug has been fixed; gates will no longer be automatically reactivated and stuck once they obtain approval.

A bug caused the total number of hours on a work item's Actual Costs page to differ from the total hours on specific Measures. An investigation found significant discrepancies between the actual cost totals and the approved hours recorded in the Timesheets; the Measure function was retrieving hours from all Timesheets whether they had been approved or not while the Actual Costs page was only calculating approved hours.

This bug has been fixed; the grand total hours calculated on Measures will now match the total hours on the Actual Costs page.

A bug prevented Metric Bulk Actions from applying changes to PowerSteering work items. When users ran any Metric Bulk Action, the "Results" page claimed that no instances were affected.

This was not a case of filtering too many work items or Metrics; the Metric Bulk Actions job was fully expected to run successfully.

This bug has been fixed; users can once again successfully run their Metric Bulk Actions without error.

A bug prevented Metric Templates from behaving correctly when the "Required only when there is data on the line" Tag and Custom Field checkbox was selected. When this was selected, Metrics created from the Metric Template would require users to provide a value for "required" Tags and Custom Fields before any numeric data was entered on a line item. The expected behavior is different; the Metric should only require the Tag or Custom Field to contain a value if data already exists on the line item.

This bug has been fixed; the "Required only when there is data on the line" checkbox once again works as expected. When the checkbox is selected, Tag or Custom Field values will only need to be provided if numeric data exists on the line item.

A bug prevented users from editing work start and end dates while adding new work items in Project Central. When any constraint type aside from "ASAP" was selected, the dates would be grayed out and uneditable. After the work item was saved, users could reopen it and edit the dates.

This bug has been fixed; dates will no longer be grayed out while adding new work items to Project Central.

A bug prevented PowerSteering work items from saving changes to Tag values. When users edited the value of a Tag and saved their changes, none of the changes would be reflected. Furthermore, the work item's History page did not log any edits to the Tag value.

This bug has been fixed; changes to Tag values will once again be saved in PowerSteering.

A bug caused the "Effort Reconciliation by period" reports to miscalculate the total number of effort hours. When users ran the report, their totals would not match the total number of allocated hours from a work item's Resource Planning page.

This bug has been fixed; the "Effort Reconciliation by period" report will include accurate totals.

A bug caused certain reports to display incorrect Metric values. These values would be different on other PowerSteering pages, such as the Program Console and Measures.

This bug has been fixed; reports will once again display correct Metric values.

A bug prevented PowerSteering's high contrast option from applying to the new Timesheet page. Users who selected the "View in high contrast" checkbox on their preferences page would not see the new Timesheet page in high contrast upon navigating to it.

This bug has been fixed; the new Timesheet page is now available in high contrast.

A bug caused values to be duplicated in certain Upland Analytics reports. In many cases, these incorrect values would be doubled or tripled in the report.

An investigation found that this error would occur when a specific Custom Field was added to the report.

This bug has been fixed; duplicated values will no longer appear when a Custom Field is added.