Friday, April 19, 2024
1 change · saas-17.2
Resolved issues and error corrections
When users follow a scheduling conflict from Field Service and create a task from an empty slot, the new task now keeps Field Service selected instead of becoming private. This prevents accidental private tasks and keeps scheduling work in the right operational workflow.
Original PR description
Steps to reproduce: - Open Field Service - Create a task so that a conflict b/w task is created - Click on the conflicting task and click on edit - In the form a conflict warning is shown - Click on 'Check It Out''. - In the view opened view click on any empty slot Issues: - The issue is that in the opened form Field Service is not selected as default project the task is set to 'Private' Cause: - Missing context causing this Solution: - Passing a context in the action window solves the issue. task-385083