See below for what's included with Inspire Planner's October 2025 - Maintenance 2 ().
Released To:
All Environments: January 19, 2026, at 10 PM ET
Available In:
All Environments: January 20, 2026
Please note:
Content in this release notes are subject to change until January 19, 2026.
Fixed an issue where undoing the deletion of a Project Task with assignments could cause related Salesforce Tasks to be incorrectly removed.
Previously, if a user deleted a Project Task, did not save, and then used Undo, the related Salesforce Tasks were still marked as deleted and were not restored. This occurred because the Project Deleted flag on Salesforce Tasks was being set before the deletion was saved.
This has been resolved so that the Project Deleted flag is only set after the deletion is explicitly saved, ensuring that undoing the action correctly preserves the related Salesforce Tasks.
Fixed an issue where users marked as Timesheet Manager in their Resource Profile could edit other users’ timesheets and time entries without having the Resource Manager permission set assigned. Editing permissions are now correctly enforced based on assigned permission sets.
We addressed a permissions gap affecting timesheet and time entry approvals. Previously, users with the Timesheet Manager permission had broader access than intended, allowing them to update approval statuses even when they were not the assigned approver. We also found that users could change the status of their own records.
With this update, timesheet and time entry status changes are now restricted to the designated approver, ensuring proper approval control and data integrity.
Fixed multiple display issues in the Portfolio Homepage Lightning Component.
The component has been optimized to handle large portfolios more reliably, preventing errors and ensuring it loads as expected.
We resolved an issue reported where the TeamEffortRollupBatch job failed with the error “Too many query rows: 50001.”
This occurred when the batch attempted to process Projects with a very high number of related Project Tasks, causing Salesforce’s 50,000-row query limit to be exceeded.
The batch job has now been enhanced to handle large data volumes more efficiently by supporting dynamic batch sizing. This prevents the query limit from being reached and ensures the TeamEffortRollupBatch runs reliably without manual intervention.
Resolved an issue where Sync Queue processing could stall under certain conditions involving failed records and system limits. Queue handling has been improved to ensure reliable and consistent processing.
We resolved an issue where the Gantt Width value in Print Settings affected row height in exported PDFs.
We aligned formatting for Project Details in the External Project Portal to ensure a consistent user experience. What's included in this release:
We resolved an issue in the external project portal where the “Remember Me” option stopped working after recent enhancements. The portal now correctly remembers the user’s login email, eliminating the need to re-enter it on each visit.
Fixed an issue in Static Portfolios where row numbers were not updated after dragging and dropping or sorting rows. As a result, row order changes were previously lost after refresh. Row positions are now saved correctly and persist as expected.
The email template has been updated to exclude the project link since Salesforce recommends a certain syntax for referencing related records, but email templates don’t actually support it. Because of this limitation, we’ve removed the Project reference from the email template.
Although we've removed the project reference from the Inspire Planner package, you will need to manually edit the email template in your org and remove the project reference.
To include the project name in the task assignment notification email, you will need to create a custom formula field on the Salesforce Task object and then update the email template to use that field.
This section contains fixes we've made specific to the Gantt LWC.
We resolved an issue affecting Gantt LWC projects using Forward Scheduling in Manual mode. Tasks were being assigned constraints automatically, leading to scheduling conflicts:
Tasks without predecessors were incorrectly receiving a Finish No Later Than constraint.
Tasks with predecessors were incorrectly being assigned a Must Start On constraint, which produced unexpected scheduling conflicts.
These constraints are no longer applied automatically, and tasks now schedule correctly under this configuration.
We resolved an issue where Custom Lookup filtering was not working as expected. When filters were applied, the UI incorrectly displayed “No records to display” instead of showing the records that matched the criteria. Custom Lookup filters now function correctly and return the appropriate results.
We resolved an issue where selecting "None" sometimes required multiple clicks, and the field would briefly display the record ID instead of the name.
This issue has been corrected and clearing lookup values now behaves consistently and displays correctly.
We fixed an issue where clearing a Custom Lookup field (by selecting “None” or using the Backspace key) did not remove the value on the first Save. Users previously had to repeat the action for the change to take effect. The value now clears correctly on the first attempt.
We resolved an issue where unsaved changes in the Project Schedule could be lost without warning. Previously, if users had unsaved modifications and then:
navigated to another project subtab,
navigated to another tab in console,
navigated to another Salesforce tab, or
refreshed the browser,
Their changes were cleared and the “Unsaved Changes Detected” warning did not appear.
This behavior has been corrected. The system now properly prompts to save/discard changes in these scenarios.
We addressed performance issues affecting customers with large projects (1,000+ tasks), where the Gantt LWC experienced very long load times. The component has been optimized to improve loading speed and overall performance, ensuring a smoother experience for large project schedules.
We resolved an issue where copying and pasting tasks with assignments from one project to another did not include the assignments in the target project. Task assignments now copy and paste correctly across projects.
We resolved an issue where exporting a Project Plan added unwanted “” characters in front of child task names. The number of characters increased with each indent level. Exports now display task subjects correctly without extra symbols.
We identified that in some orgs, the Project Schedule was still loading slowly even after the load optimization had been deployed.
To resolve this, we optimized rollup processing which significantly improves performance for both standard and custom number and currency fields.
Additionally, we introduced a new option that allows you to disable rollups for specific custom fields.
We resolved an issue where some Task List LWC projects displayed an error when opening. The problem was caused by broken data—specifically, parent tasks with missing start or end dates. The error no longer occurs, and these projects now open as expected.
Fixed an issue where the User Default Project Layout was being incorrectly applied to Task List projects instead of only to Waterfall projects.
We resolved an issue where copying and pasting a group of tasks with dependencies caused the Predecessor field in successor tasks to be cleared. This resulted in dependencies being removed during the paste action. Dependencies are now preserved when copying and pasting tasks.
Fixed an issue in Manual Mode where dragging a task with a predecessor forward in the Gantt Chart applied incorrect constraints. Previously, a Must Start On constraint—or an incorrect Start No Earlier Than constraint with the original start date—was applied, preventing the task from being moved. The system now correctly prompts users to apply a Start No Earlier Than constraint using the new dragged start date.
This section contains items that are scheduled for or have been deprecated.
The Locked__c field on the Project object has been removed, as it is no longer used. Project locking was previously updated in IP-643 (June 2024 – Maintenance 2 release) to leverage the Lock object instead.