2025R1.3 - Resolved Issues

The 2025R1.3 version of Eclipse PPM will be deployed on Wednesday, November 22nd, 2025. This minor release will address the following high-priority customer issues. Click on any of the resolved issues below to learn more about them:

 

A bug prevented users from deleting Documents. The Delete option was missing from the dropdown menu in the Documents section, making it impossible to remove documents.

Delete Option Missing in Documents

This bug has been resolved; the Delete option now appears correctly in the dropdown menu, allowing users to delete documents as expected.

A bug caused an error message when users attempted to open or edit Task details, including updating the Description or Title and adding Comments in certain cases.

This bug has been fixed; users can now open, modify, and add comments to Task details without encountering any errors.

A bug prevented certain Resources from being added to the Resource Planner. This typically occurred when a resource had a Rate Card with fractional values (for example, $75.50/hour), which caused an error and blocked the resource from being added to the Resource Planner.

Error When Adding Resources with Fractional Rates to Resource Planner

This bug has been fixed; users can now add Resources to the Resource Planner without encountering any errors, including Resources with fractional Rate Cards.

A defect prevented users from retrieving results using certain Search API endpoints with a provided filter ID. In affected cases, the API returned a 404 error when attempting to search Projects, Tasks, Issues, Risks, Programs, or Resources using the filter.

This issue has been resolved ; Search API endpoints now correctly return results when using valid filter IDs.

A bug caused a Bad Request error when users attempted to update certain Property fields when editing Tasks. In affected cases, saving changes triggered a JSON-related validation error, preventing updates from being applied. This behavior also occurred when modifying Program Properties.

The issue has been resolved, and Property field updates now save successfully without errors.