2025R1.0 - Resolved Issues

Below is a summary of the main issues addressed by this release. Individual customer cases will be updated by the Support team through the portal. Cases will be closed out with customers upon confirmation that the issue has been resolved to your satisfaction.

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

The resolved issues in this release fall under the following categories:

 

Agents

An issue caused web browsers to crash when users accessed the Work Archival agent. When this occurred, the page would take a very long time to load before finally displaying a "This page isn't responding" error. This would force users to close the browser tab and reopen PowerSteering.

This issue occurred because the Work Archival agent generates a massive amount of logs each time it runs. Each record has the potential to retrieve thousands of sub-records, which puts a great deal of strain on the web browser.

To remedy this issue, only 100 total records will be retrieved by the Work Archival agent. Web browsers will no longer crash because of this agent.

 

API

A bug caused API calls to fail when special characters were entered into PowerSteering. For instance, special characters entered into a Custom Field value would result in an API failure.

This bug has been fixed; special characters will no longer result in failed API calls.

Login

A bug required username entries to be case sensitive whenever users reset their PowerSteering password. This issue only persisted during a password reset; a regular PowerSteering login attempt did not require a case-sensitive username entry.

This bug has been fixed; username entries no longer need to be case-sensitive during password resets.

 

Metrics

A bug caused Metric imports to overwrite locked Metric cells. Any Metric cells that are locked are not expected to be changed by Metric import files.

This bug has been fixed; uploading Metric Import files will no longer cause changes to locked Metric cells in PowerSteering.

A bug caused Metric imports to add locked beneficiaries to Metrics. Locked beneficiaries are not expected to be added to PowerSteering by uploading Metric Import files.

This bug has been fixed; uploading Metric Import files will no longer add locked Metric beneficiaries in PowerSteering.

A bug caused all saved Metric Bulk Action jobs to disappear after the 2024R1.2 Controlled Release.

An investigation into discovered that this occurred due to a caching issue. The bug has been fixed; all saved Metric Bulk Action jobs are once again visible on the Metric Bulk Actions page.

Note: There are new limitations on which users can see which Metric Bulk Actions jobs in PowerSteering. See the New Features for more information.

Users experienced slow loading times while creating or editing Metric Bulk Action jobs in PowerSteering. In particular, the "Step 2: Filter Metric Templates" portion of the process took much longer than expected to load.

This issue has been fixed; users will no longer face long load times while creating or editing Metric Bulk Action jobs.

 

Reports

A bug prevented automated PowerSteering reports from generating and data. The reports would display a "The report generated no results" message, but an investigation found that the report was correctly configured and expected to return data.

This bug has been fixed; automated reports will no longer incorrectly fail to retrieve data.

 

Tags and Custom Fields

A bug caused Tag values to automatically change without any user intervention. Specific work item Tags that contained multiple values would lose all values except for one.

An investigation found that this issue occurred due to a problem with the PowerSteering REST API. This bug has been fixed; work item Tags will no longer automatically lose their values.

A bug caused PowerSteering Tags to lose their hierarchical structure after an API call.

This bug has been fixed; API calls will once again respect the hierarchical structure of Tags.

A bug prevented all values selected on certain Tags from being displayed in PowerSteering. After selecting multiple values on a certain Tag, only some of the values would be displayed within the user interface. Editing the Tag or making an API call would reveal every selected Tag value.

This bug has been fixed; certain Tag values will no longer be hidden.

While creating multiple work items, users were able to leave required Tags without a value. Certain required Tags were not marked as required on the "Add: Multiple Work Items" page, allowing users to save their work items without entering values for the Tags.

This bug has been fixed; required Tags will be displayed as required on the "Add: Multiple Work Items" page and users will not be able to ignore them.

 

Timesheets

A bug prevented Timesheet data from translating to Actual Cost data on a work item. When specific users entered time against a work item, Actual Cost data for the user would not be displayed for all dates on the work item's "Actual Costs" module.

This bug has been fixed; "Actual Cost" modules will no longer omit Timesheet entries on certain dates.

Upland Analytics

Multiple Upland Analytics reports would fail to load. The loading time would exceed the 10 minute limit, resulting in a timeout.

This issue has been resolved; Upland Analytics reports will no longer result in timeouts.