On Kabissa, we have started using discourse to track todos. We put the status in parentheses at the end of the title. It works reasonably well.
Here's a copy/paste of our todo guidelines.
We are using discourse topics to track volunteer tasks.
Title should clearly describe the task. Indicate urgency if needed with URGENT at the front. Indicate status (new, in progress, resolved, feedback, closed, rejected) in parentheses at the end.
URGENT: Make sure backups to amazon s3 are running on www.kabissa.org (new)
Tags should include
todo as well as any relevant categorization to help with finding this todo later, e.g.:
todo backups civicrm drupal
Category should be appropriately set, e.g.:
Volunteers > Platform
First line should mention the person who is being asked to do this task, e.g.:
@schnippy can you look at this?
The rest of the first post in the topic should explain the todo as clearly as possible, preferably with a clearly stated acceptance test, e.g.:
Acceptance Test: When I log into the amazon s3 panel and browse to the kabissa backups folder, I can see the list of recent backups. When I download one I can verify it is not corrupted and working fine as a backup. These include nightly backups for kabissa and civicrm databases, weekly backups of files, and weekly backups of files and databases.
When you take on a task, change the title to reflect its status and add a reply to indicate you are taking it on.
As the task moves through to completion, continue to reply to it to record any information or to ask questions. Change the title to change the status as needed.
When a todo topic is completed, close it!