A new Intervals user asked us about re-occuring task support for monthly tasks.
At present Intervals does not have true "re-occurring" tasks but there is a quasi way to do it. What we do is track the time, make updates, notes, etc. and then use the "copy task" link on the left hand side of the task detail page. So we close out the task for the given month, then spawn it's twin for the next month. We actually tinkered with true "re-occurring" tasks, but found that it created too many tasks and created overload so we decided to focus on one task at a time. "Copy" task creates a new task # but with the same summary, project, module, etc. then we schedule it for the next month. In fact, we often "copy" a task for a given project to a new project.
We are in the process of adding more flexbility to tasks within Intervals. Specifically we are removing the due date requirement and allowing a task to be assigned to noone or multiple people. Since we are adding in more flexbility, it seems like a good time to revisit recurring tasks. We are considering adding recurring tasks that are not true recurring tasks, but serve the same purpose.
Here is what we are thinking:
1. create task 2. make it recurring 3. select the recurring interval (weekly, daily, monthly, etc.) 4. instead of cluttering up the system with a bunch of tasks, only create the new task if: a. the due date has passed b. the current task is marked as closed
Here is a quick real-life scenario. I have a weekly backup rotation task assigned to me in our Pelago IT project. Presently, I rotate the backup, make notes on the task, then update it and move it to the following week. With recurring tasks, I would do the same steps but instead of scheduling the task out a week I would close the task. When the task it closed the recurring rule would know to create a new task with the same information due next week.
Would you use it? Is the complexity a necessary and welcome addition? Do you need more or less?