[FEATURE] Repeating Tasks on a Schedule

[acul009]

Is your feature request related to a problem? Please describe. I need a "Project Management"-Software to manage the daily tasks of my MSP. The Issue here is, that some tasks are always the same and done on a schedule. This is important for out monthly server Maintenance.

Describe the solution you'd like I would like to be able to setup a task on a schedule. This could be every 10th of the month, or even better something like the second Saturday of the month. At the given day, leantime would automatically create either a copy of the completed task, or a new task from a template. If the task is a copy, it should reset all checkboxes and subtasks.

Additional context While it might not be traditional to manage weekly or monthly tasks like that, it would allow me to have reports of when those maintenance runs were done and the ability to comment on them.

[marcelfolaron]

Hi,

Thanks for the feature request. I have been struggling to get the workflow right for repeat tasks. For example, say I need to do something on every 10th.

• when do you expect the task to be visible?
• • right after the last one finished?
• • months in advance?
• • few days before?
• what if you need to change the repition? Which task would you edit? Or should it be a complete separate flow?

It‘s an interesting concept since the task should indeed be copied to allow for effective time and progress tracking.

I am just not sure how to get it into the system effectively.

On Sat, Jan 21, 2023 at 5:43 PM acul009 @.***> wrote:

Is your feature request related to a problem? Please describe. I need a "Project Management"-Software to manage the daily tasks of my MSP. The Issue here is, that some tasks are always the same and done on a schedule. This is important for out monthly server Maintenance.

Describe the solution you'd like I would like to be able to setup a task on a schedule. This could be every 10th of the month, or even better something like the second Saturday of the month. At the given day, leantime would automatically create either a copy of the completed task, or a new task from a template. If the task is a copy, it should reset all checkboxes and subtasks.

Additional context While it might not be traditional to manage weekly or monthly tasks like that, it would allow me to have reports of when those maintenance runs were done and the ability to comment on them.

— Reply to this email directly, view it on GitHub https://github.com/Leantime/leantime/issues/1322, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALG4EFV4O3ISD436F3PAC53WTRQ7XANCNFSM6AAAAAAUCUFG6I . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[acul009]

My perfect solution would probably look like this:

1) I can select a schedule for creating a task. This should allow for fixed scheduling (allowing cron syntax would be nice, that would allow things like 3rd saturday of the month). It should also give me a delta based option (e.g. 30 days after the task was closed) The new task should be created right on schedule

2) I can select a delta for the due date and working days. (e.g. due after 7 days) This would then be used to calculate the new dates after creating the new task.

1 & 2 would together allow you to control when the new task should appear and when it would be worked and due.

3) for the repetition I would see 3 options.

I think the nicest to use would be a Seperate menu for template tasks which would be cloned into actual tasks. That Would allow me to view all my scheduled tasks easily, but it would probably involve the most work. This option coud also be used to prepare task templates which could also be manually used to create a task. e.g.: create a new issue using the server-installation template which would contain a checklist containing has to be done when setting up a new server. (a bit like mattermost playbooks)

The next option would be to have a menu only for repetition cycles and all tasks would point to that cycle, which means changing one would change all

The easiest option would be to just always use each ticket once for cloning and then mark it as "used" That way the option would only work on the newest task, which hasn't been cloned yet.