2024R1 - Resolved Issues

A bug caused text formatting to be excluded from content retrieved from the /api/services/projects API endpoint. Integrations built using this endpoint would successfully retrieve the actual text, but any formatting (bullet lists, line breaks, etc.) would not be included.

This bug has been fixed; content retrieved from the /api/services/projects API endpoint will once again reflect any formatting that has been implemented in Eclipse PPM.

Note: This is one of the XML-based endpoints that will be deprecated with the 2024R2 release expected later this year. Any existing API integrations should be migrated to the new JSON-based API endpoints as soon as possible. Integrations built using the XML-based endpoints will no longer function properly.

A bug caused inconsistencies when users would group their Projects by Status on the Dashboard. When this occurred, groups would sometimes contain Projects with different Statuses. When the Projects on the Dashboard are grouped by Status, each group is expected to only contain Projects of a specific Status.

This issue would appear intermittently in Eclipse PPM; users would revisit the Dashboard to find the Projects grouped as expected, and then return to it later to find it grouped incorrectly.

This bug has been fixed; users can once again successfully group their Projects by Status on the Dashboard.

A bug caused Project Status Updates to lose any implemented formatting when viewed on a Project Dashboard. On the Home page, the "Status / Health" window would display the correct formatting:

However, the "Status / Health" window on the Project Dashboard would display the Status Update text without any of its original formatting:

This bug has been fixed; Status Updates will keep their formatting when viewed through the Project Dashboard.

A bug caused text fields in Eclipse Docs to lose certain formatting elements when users viewed the document's content and opened the "Mail Merge" tab. For instance, bullet lists would appear as full paragraphs without line breaks and certain words would overlap with each other. When users view merged data on Eclipse Docs, the text fields are not expected to be altered in any way.

This bug has been fixed; Eclipse Docs will no longer lose their formatting when viewed on the "Mail Merge" tab.

A bug prevented certain Financial Plans from successfully calculating "Actual" Resource costs as Expenditures on certain Projects. When these Projects were configured to "Calculate actuals using time entries", the labor Expenditures under "Actuals" would remain at zero after Resources would enter time against the Project. When this occurs, labor costs under "Actuals" are expected to calculate based on time entered against the Project as well as Resource rates on the Work Planner.

This bug has been fixed; labor Expenditures under "Actuals" will once again be calculated based on time entries when "Calculate actuals using time entries" is selected for the Project.

An error prevented certain Projects from appearing on the "Projects" view of a Program. Certain Programs would display an error on their "Projects" pages stating that certain Projects were "hidden" from the "Program Projects" list:

The error claimed that users did not have adequate permissions to view all the Projects, but this was incorrect. Even users who had permissions to view all Eclipse PPM Projects would see this message.

This error has been fixed; users with adequate permissions will no longer see this error message and will be able to view all Projects on a Program's "Projects" view.

A bug prevented users from successfully running certain reports as Microsoft Excel files in Eclipse PPM. When one of these reports was opened with Excel, an error window would appear claiming that the content of the report contained problems that required repair. After dismissing this error message, another error message would claim that certain content within the file that were deemed "unreadable" may have been discarded.

This issue has been fixed; downloading reports as Excel files will no longer cause any errors.

An error would occur when the Eclipse PPM Excel Add-In was used. When users selected the Eclipse PPM tab in Microsoft Excel and then selected the Refresh button, an internal server error message would appear:

An investigation found that this issue occurred due to a bug with the /api/reports/adhocOld/{id} API endpoint. This bug has been fixed; the Eclipse PPM Excel Add-In will no longer produce a server error when users select Refresh.

Reports created using the "Project Objectives List" data source in Upland Analytics would not pull any data. Instead, users would receive a "No Data Available" error message.

This bug has been fixed; reports created with the "Project Objectives List" data source will once again populate with the appropriate data.

A bug caused Upland Analytics reports created with the "Project List" data source to contain incorrect values in the "Allocated Effort" column. Reports would multiply the allocated effort on multiple Projects, resulting in a large discrepancy between the reported value and the true amount.

This bug has been fixed; Upland Analytics reports will no longer misrepresent the "Allocated Effort" on Projects.

A bug caused Project Filter rules to automatically change the selected "Created Date" after saving. If a user created a new custom Project filter with a rule for the Created Date, the selected Created Date would change to a different date once the filter was saved.

This bug has been fixed; custom Project filters with a "Created Date" will no longer change dates once the filter is saved.

A bug caused the "Date Reported" field of a Risk to change unprompted during editing. When users navigated to a Risk and selected the Edit Riskbutton, the "Date Reported" field would contain a new date even though the user did not interact with the field at all.

This bug has been fixed; the "Date Reported" field will no longer change while editing Risks.

A bug prevented Projects from appearing on the Template Application History page of Project Templates. In each case, Projects had been creating using the template, which means they were expected to appear listed on the page.

This bug has been fixed; Projects will once again be listed on the Template Application History page if they have been created using the Project Template.

Users were unable to adjust certain Tasks components through the Task window on the Work Planner. For instance, when users would open up a Task, navigate to the "Resources" tab and change a Resource's "Units (%)" value, the Save button remained grey and inoperable. When users close the Task window without saving, their changes are immediately discarded.

An investigation found that this was not a bug; the Save button was inoperable because the Tasks contained mandatory custom Properties that needed to contain values before the Task window could be saved. However, there was no way for users to know what the issue was if they were editing any of the Task window tabs aside from "Properties". To remedy this, a red asterisk will now be placed on the "Properties" tab when the Task contains mandatory Properties without values:

This will let users know that the Properties need to be addressed before the Task can be saved.

A bug prevented users from saving descriptions on Tasks. While editing a Task's details through the Work Planner, users would enter text into the "Description" field that would not always be saved to the Task after selecting the Save button. Although Task descriptions were sometimes saved successfully, the behavior was inconsistent.

This bug has been fixed; Task descriptions will always be saved after the user selects the Save button.