From 0371acff89b14b9bdcb03e72fd9637e26e6b517c Mon Sep 17 00:00:00 2001 From: Frederic Guillot Date: Sun, 29 Jan 2017 11:07:42 -0500 Subject: Move English documentation to folder en_US --- doc/en_US/recurring-tasks.markdown | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/en_US/recurring-tasks.markdown (limited to 'doc/en_US/recurring-tasks.markdown') diff --git a/doc/en_US/recurring-tasks.markdown b/doc/en_US/recurring-tasks.markdown new file mode 100644 index 00000000..d2385feb --- /dev/null +++ b/doc/en_US/recurring-tasks.markdown @@ -0,0 +1,24 @@ +Recurring tasks +=============== + +To fit with the Kanban methodology, the recurring tasks are not based on a date but on board events. + +- Recurring tasks are duplicated to the first column of the board when the selected events occur +- The due date can be recalculated automatically +- Each task records the task id of the parent task that created it and the child task created + +Configuration +------------- + +Go to the task view page or use the drop-down menu on the board, then select **Edit recurrence**. + +![Recurring task](screenshots/recurring-tasks.png) + +There are 3 triggers that currently create a new recurring task: + +- Moving a task from the first column +- Moving a task to the last column +- Closing the task + +Due dates, if set on the current task, can be recalculated by a given factor of days, months or years. +The base date for the calculation of the new due date can be either the existing due date, or the action date. -- cgit v1.2.3