2024R1.2 - Resolved Issues

The 2024R1.1 release introduced Metric Bulk Action jobs, which allow users to save their Metric Bulk Actions and schedule them to run later. However, the original implementation allowed all existing jobs to be edited by anyone with access to Metric Bulk Actions.

With this release, Metric Bulk Action jobs can only be edited by their creators or PowerSteering administrators. This will prevent any unwanted changes to scheduled jobs.

A bug prevented default values of "0" from appearing on new Metric instances. When a Metric Template's line items were configured to display default values of "0", the expected values would not automatically apply to Metric cells when a Metric was added to a new work item. Once a user edited the numeric values of one of these line items, the default zeroes would appear after saving. However, default values are expected to be displayed before any edits to the Metric occur.

This bug has been fixed; default values of "0" will now appear on Metrics before the Metric line items are edited.

A bug prevented users from being able to edit basic work item details without the "Edit Controls" Project permission. When users without this permission selected the Edit All Details button, they were unable to save their changes. An error message claiming that they did not have permission to edit the work item's controls.

Users are not expected to require the "Edit Controls" permission to edit the work item's basic details; the "Edit Controls" permission is only required for enabling work item settings to turn on scheduling, web folders, and cost modules.

This bug has been fixed; users will no longer be prevented from editing basic work item settings without the "Edit Controls" permission.

An issue caused PowerPoint template uploads to fail if any of the files slides did not contain any placeholders. Users who attempted this would receive a "500 Servlet Exception" error.

To fix this issue, PowerSteering now accepts PowerPoint template slides that do not contain placeholders. When a slide does not have any placeholders, “No Change“ can be selected while defining a PowerPoint template.

An issue prevented Portfolios from displaying all of the intended work items. A configuration check showed that no work items were being filtered out due to Portfolio settings.

An investigation found that this issue occurred because of duplicate work status name. The issue has been identified and fixed; Portfolios will no longer needlessly filter out intended work items.

An issue caused PowerSteering reports to be sent to no-access users. Users with the "No-Access User" checkbox selected on their profiles would still receive reports. This is not the expected behavior.

With this release, the choice is now up to the customer. Reports will not be sent to no-access users by default, but if you would like no-access users to receive PowerSteering reports, speak to your PowerSteering representative to enable this for you.

A bug prevented PowerSteering reports from running and being sent out to subscribers. Certain reports would display the expected run time in the "Last Run" column, but they were never successfully executed and sent out to the intended email recipients.

This bug has been fixed. Reports will once again run and send themselves out to the intended recipients on schedule.

A bug prevented certain reports from displaying data from the previous week. In order to display this data, reports would need to be opened and re-saved. These reports were expected to display data from the previous week as soon as a new week started.

This bug has been fixed; PowerSteering reports will no longer omit data from the previous week.

A bug prevented custom Summary page widgets from displaying negative numeric values. These values would be negative upon entry and they would be displayed as negative integers on other PowerSteering components (i.e. PowerSteering reports). However, the values would be displayed as their positive counterparts on custom Summary page widgets.

This bug has been fixed; negative values will be properly displayed on custom Summary page widgets.

A bug prevented PowerSteering users from including "@" symbols in their "URL" type Custom Field values. If an "@" symbol was entered, the Custom Field would not be saved and a "Please enter a valid email address" message would appear.

An investigation found that URL values with "@" symbols were being mistaken as email addresses instead of URL links. This bug has been fixed; users can once again save "@" symbols in the "URL" type Custom Fields.

An issue prevented reports from loading in Upland Analytics. When a report was selected, the page would continuously load and the report would fail to appear before the 10 minute timeout limit was reached. In some cases, users were not even able to access Upland Analytics at all.

An investigation into the issue found that it was originally occurred due to change made to the Exchange Rates table. This triggered a process to rebuild the Metrics data cache table, which failed. The process continuously retried for several hours until if was finally able to complete. During this time, however, the Upland Analytics reports that required Metric data were blocked. This caused instability on the part of Upland Analytics, which resulted in failed reports. The situation was made worse because of the accumulation of report queries that were waiting for data.

With this release, a fix has been introduced to avoid overloading the database server when this occurs in the future. Upland Analytics reports can once again be loaded without timing out.

A bug prevented Upland Analytics reports from displaying data when a Program filter was being used. Once a user attempted to filter the report by specific Programs, the report would fail to load.

An investigation found that this problem occurred because Upland Analytics was adding an additional space to Program names. When users chose a Program to filter by, Upland Analytics would not recognize the Program in PowerSteering, which meant it would not pull any actual data.

This bug has been fixed; Upland Analytics will not properly recognize Program names, which means Program filters will no longer prevent data from displaying.

A bug prevented certain users from viewing all work items on Upland Analytics reports. When specific users downloaded a report, they would not be able to see all of the intended work items listed on the report. When other users downloaded the report, they were able to see the missing work items. A permission check verified that this error was not the result of certain users not having the required permissions.

This bug has been fixed; users will once again be able to see all intended work items when they download an Upland Analytics report.

A bug caused Upland Analytics reports to display incorrect results for Status Update frequencies on work items. For instance, Upland Analytics reports would display frequencies of "Weekly" or "Monthly" even when Status Report frequencies were turned off on certain work items.

An investigation found that this was the result of PowerSteering being unable to detect changes made to Status Report frequencies on work items. The bug has been fixed; proper Status Report frequencies will once again be reflected in Upland Analytics reports.