summaryrefslogtreecommitdiff
path: root/doc/recurring-tasks.markdown
diff options
context:
space:
mode:
authorFrederic Guillot <fred@kanboard.net>2015-08-29 20:00:53 -0400
committerFrederic Guillot <fred@kanboard.net>2015-08-29 20:00:53 -0400
commit6c711f696f73bc59813f6834ec241aef3b626cbd (patch)
treeded4f0e8c7f8c672414ff3f2f84eac0f6d9073e5 /doc/recurring-tasks.markdown
parentef087f5e22df1a0d97babef26aaf9b8960ee6d5d (diff)
Include documentation in the application
Diffstat (limited to 'doc/recurring-tasks.markdown')
-rw-r--r--doc/recurring-tasks.markdown24
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/recurring-tasks.markdown b/doc/recurring-tasks.markdown
new file mode 100644
index 00000000..b1de8d05
--- /dev/null
+++ b/doc/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 occurs
+- 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 dropdown menu on the board, then select **Edit recurrence**.
+
+![Recurring task](http://kanboard.net/screenshots/documentation/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.