|
|
|
|
|
by cpach
169 days ago
|
|
For recurring and future tasks that are not automated and is not tracked by any other process I have a page in Confluence Cloud. It contains a table where one column has the due date and the other column a short description of the task. Then I have a weekly reminder that reminds me to look at this page. If it’s time to do the task but it’s so big that I cannot do it directly I will create a Jira ticket for it. When the task is done I either remove it from the list, or bump the due date if it’s a recurring task. |
|
The cases I’ve been thinking about are team-level recurring tasks, where execution and ownership need to be visible beyond a single person.