Fixed an issue where adding a multi-select custom field to the Project Task Field Set and populating the field in Gantt LWC resulted in an error.
 

Multi-select custom fields can now be added to the Project Task Field Set and populated in Gantt LWC without generating an error.

Baseline dates populated for project tasks were not displayed in the Task Dialogue. The issue has been resolved, and baseline information is now displayed correctly.

Fixed an issue where the parent task arrow and assigned resources avatars in the Gantt View increased in size after switching from the Calendar View to the Gantt View.
 

Previously, opening a Project in Calendar View and then switching to Gantt View caused these icons to appear larger than expected. Refreshing the browser restored them to their normal size.
 

The icons now maintain their correct size when switching between Calendar and Gantt Views.

Fixed an issue where filtering certain project task fields displayed unexpected code-like values instead of user-friendly options.
 

This issue affected the Done, Multi Role, and Critical fields. Filters now display the appropriate user-friendly values for selection.

Gantt loading performance has been improved to provide a faster and more responsive experience.

Fixed an issue introduced in the JUL 2026 Major Release where filtering by Assigned To using the Column Quick Filter bar in the Task List returned no results.
 

The Assigned To filter now correctly returns project tasks that match the selected resource.

Updates made in the Gantt UI were not always reflected immediately. In some cases, users had to exit the edited cell by pressing Enter, Tab, or clicking outside the cell before the updated value was displayed.
 

This issue has been resolved. Updates are now reflected immediately in the Gantt UI, including Finish Date changes resulting from Duration edits and row color selections.

Fixed an issue where the Chatter red notification indicator on project tasks remained visible after the Chatter panel was opened and closed.

Fixed an issue in the Project Calendar View where users with Viewer access could create Appointments despite having read-only access to the Project.
 

The same issue occurred when the Project Record Page had Read-Only Mode enabled.
 

Appointment creation is now restricted for users with read-only access, ensuring that Viewer collaborators and users accessing Projects in Read-Only Mode cannot create Appointments.

Fixed an issue where the Column Quick Filter in both the Gantt LWC and Portfolio LWC displayed incorrect values for the following fields:

• Multi-Role
• Ready to Start
• Time Tracking Only
• Done
   

These fields now display the correct values when using the Column Quick Filter.

Fixed an issue where the Calendar did not retain the currently selected date after a refresh. Previously, refreshing the page caused the Calendar to move back by one day, with each subsequent refresh shifting the displayed date back another day.
 

The Calendar now correctly retains the selected date when the page is refreshed.

Fixed an issue in Task List Projects where entering a past Finish Date on a project task and refreshing the page could result in an error message. The schedule would then become inaccessible, with the loading spinner continuing indefinitely.
 

The issue has been resolved so that project tasks with past Finish Dates are handled correctly, preventing the error and ensuring the schedule remains accessible after a refresh.

Fixed an issue where Task List projects were referencing the incorrect custom field set.

Fixed an issue where Resource Utilization opened from the Project UI incorrectly displayed “No records to display” even when resource utilization data was available.
 

Resource records now load correctly in Resource Utilization when accessed from the Project UI.

Fixed an issue where Standard Users were unable to edit their own time entries directly from the Time Tracker Weekly View while the Timesheet was Open. Previously, clicking Save after modifying an entry displayed an error and the changes were not saved.
 

Standard Users can now successfully update their time entries from the Weekly View and save their changes as expected.

Fixed an issue in the Resource Utilization component where searching for resources by name could fail to return results after previously filtering and pinning resources.

Resource name searches now return the expected results without requiring a manual page refresh.

Fixed an issue in Resource Utilization where filtering by a date range did not immediately update the results.
 

Previously, users had to manually refresh the page after selecting a date range for the filter to take effect. The date range filter now applies correctly without requiring a page refresh.

Fixed an issue where creating a second Booking Task for a resource caused both Booking Tasks to move to the top of the project schedule. Previously, the first Booking Task was initially displayed at the bottom as expected, but creating a subsequent Booking Task incorrectly changed the position of both tasks.
 

Booking Tasks now maintain their correct position in the project schedule when additional Booking Tasks are created.

Fixed an issue where picklist dropdowns, such as Language and Work Week Start, were incorrectly constrained within their section when editing a Resource from the Resources tab. Previously, the dropdown options could be partially hidden, requiring users to scroll within the section to view and select an option.
 

Picklist dropdowns now display correctly on top of surrounding content, providing a more consistent and accessible user experience.

Fixed an issue where certain parent rollup records could generate a System.NullPointerException error when processed by the parent task rollup job.
 

Previously, under certain conditions, the Update Parent Tasks batch job could encounter a null value while creating an updated project task, causing the job to fail with an error.
 

The rollup process has been updated to handle these records correctly and prevent the error from occurring.

The Enable BETA Features setting has been updated to clarify that administrators can choose whether to enable BETA features in their Production org.
 

The previous “Not recommended for Production orgs” message has been removed to avoid implying that BETA features cannot or should not be enabled in Production. Administrators can now make this decision based on their organization’s requirements and comfort with using features that are still in preview.