Currently jobs are created when the controller becomes aware, with the exception of recurring jobs that auto-populate. It would be helpful to mask jobs on the controller dashboard that don't need immediate action/despatch.
For instance, often DBM pickups are scheduled up to a week in advance, but these appear as pending jobs as soon as created, making the dashboard busier than needed.
With a category that could be viewed separately (for offline planning) in which the jobs are promoted to the controller dashboard only on the day they are due, the controller would not get distracted with jobs they don't need to action.
Currently jobs are created when the controller becomes aware, with the exception of recurring jobs that auto-populate. It would be helpful to mask jobs on the controller dashboard that don't need immediate action/despatch. For instance, often DBM pickups are scheduled up to a week in advance, but these appear as pending jobs as soon as created, making the dashboard busier than needed. With a category that could be viewed separately (for offline planning) in which the jobs are promoted to the controller dashboard only on the day they are due, the controller would not get distracted with jobs they don't need to action.