Multiselect Tasks on Gantt and Kanban

Highlights

Select multiple Project Tasks at once to delete or reorganise them in a single action - no more repeating the same operation task by task.

What Changed

Project Tasks on the Gantt and Kanban can now be selected in bulk using Shift+click, Cmd/Ctrl+click, or drag selection (Kanban only). When multiple Tasks are selected, the context menu adapts to show available bulk actions. Tasks can be deleted together in a single transaction or reorganised by indenting, outdenting, or moving them within the hierarchy. Errors during bulk operations preserve the current selection so users can identify and resolve individual issues without starting over. The delete confirmation modal has also been updated to list all affected Tasks.

How It Works

1. Select Tasks using Shift+click to select a range, Cmd/Ctrl+click to select individual Tasks, or click and drag across cards on the Kanban
2. Right-click any selected Task to open the context menu
3. Choose Delete to remove all selected Tasks in one action or use Indent/Outdent (Gantt only) to reorganise the hierarchy
4. If any Tasks cannot be processed due to permissions or structural constraints, an error toast identifies which Tasks are affected and the selection is preserved

Enablement Guidance

No manual steps necessary.

Dependency Rescheduling and Performance Improvements

Highlights

Task dependency rescheduling is now more reliable and consistent across complex project structures, and large Task Templates with 500 or more tasks now import without hitting Salesforce limits.

What Changed

The Task rescheduling engine has been replaced with a new algorithm that processes dependency changes in a single, deterministic pass. Rescheduling now produces consistent results regardless of whether Tasks are moved forward or backward, and locked Tasks are handled correctly - only explicitly locked Tasks stay in place, while their siblings reschedule as expected. Parent Task date ranges update accurately as a rollup from their children. False circular dependency errors that previously appeared on large task sets during Template validation are also eliminated. Separately, roll-up calculations are now deferred during Task Template imports and run once after the import completes, allowing templates with 500 Tasks to import successfully.

How It Works

• Move or reschedule a Task with Dependencies - Successors and Parent Tasks update in a single operation with no repeated recalculations
• Lock a Task to keep it in place while dependent siblings reschedule around it
• Import large Task Templates - the import completes without errors, with correct Parent dates, Subtask counts, and Phase aggregates after completion

Enablement Guidance

No manual steps necessary.

Log Time Invocable Action

Highlights

Log time against any Salesforce object using a new Invocable Action, enabling customers to build Flows and automations that report time directly into Precursive Timesheets without users needing to leave their working context.

What Changed

A new Apex invocable action is now available for use in Salesforce Flows and automations. It accepts a Task or Task Category, Hours, Date, Participant, and optional Comments, and handles the full Timesheet hierarchy automatically - creating the Timesheet, Line Item, and Entry if they do not already exist, or adding to an existing entry if one is found for the same date and Task Category. Comprehensive validation and error handling is included, covering permission checks, inactive Resources, archived Projects, leave Phases, and Timesheet status.

How It Works

1. Add the Log Time invocable action to any Salesforce Flow
2. Pass the required inputs: Participant, Hours, Date, and either a Task or Task Category
3. The action creates or updates the relevant Timesheet, Timesheet Line Item, and Timesheet Entry automatically
4. If any validation fails, a descriptive error is returned to the Flow for handling

Enablement Guidance

No manual steps necessary. The invocable action is available immediately after upgrade. Customers wishing to use it should build a Salesforce Flow that calls the action with the required inputs. Participant and Task Category records must be created on the customer side before the action is called.

What Else Changed

• Milestone Timeline now displays all Milestones linked to Phase Tasks, including those without Milestone Progress records
• Projects assigned to a Team or Region now appear correctly for members after sharing recalculation, even when the Project has no Phases
• Task Owner is now correctly preserved when reassigning a Contributor in the Manage Contributors modal
• Resource Supervisor can now be updated even when the Resource is a Participant on an archived Project
• Supported Currencies in Precursive HQ now displays all configured currencies correctly and saves changes reliably

Data Model

No changes in the Data Model in 2.21 release.