We are in the process of standardizing various processes we go through for repetitive projects like Exchange Migrations, New User Set-Ups etc.
These processes/projects have long lists of items that must be executed for the item to be considered complete.
I'd like to suggest some method of creating such lists within a Task as opposed to having to create separate tasks for each step.
This would allow the technician to have a nice clean list for their review which they can check off as they go through ensuring they don't miss any steps along the way. Visually this would be represented by small checkboxes next to the title for each Task Step that the user would check as they progress.
This would give the user a good visual indicator of where they are within a project and Managers could also review these lists to see if any steps were missed or how long each step may have taken (assuming the tech logs the time) so that we can understand how long these processes are taking on average or follow-up with a technician when steps are being skipped to understand why.
This could also help to build a foundation for a future Project module which could go deeper to allow users to create Project Phases which could each contain start-stop dates, time/cost estimated and Task Lists outlining all the items that need to be done in order for a particular Task/Phase to be considered complete.
These processes/projects have long lists of items that must be executed for the item to be considered complete.
I'd like to suggest some method of creating such lists within a Task as opposed to having to create separate tasks for each step.
This would allow the technician to have a nice clean list for their review which they can check off as they go through ensuring they don't miss any steps along the way. Visually this would be represented by small checkboxes next to the title for each Task Step that the user would check as they progress.
This would give the user a good visual indicator of where they are within a project and Managers could also review these lists to see if any steps were missed or how long each step may have taken (assuming the tech logs the time) so that we can understand how long these processes are taking on average or follow-up with a technician when steps are being skipped to understand why.
This could also help to build a foundation for a future Project module which could go deeper to allow users to create Project Phases which could each contain start-stop dates, time/cost estimated and Task Lists outlining all the items that need to be done in order for a particular Task/Phase to be considered complete.
Comment