RTM as issue tracker/task manager
(closed account) says:
We are a small development team working on web applications. We tried JIRA and Redmine to track bugs, tasks, etc., but then realized that RTM could suit our needs perfectly.
Each of us has an RTM account, and there is also a master Inbox account that all developers keep open. We have added each other and the master inbox as contacts in RTM.
We give users an email address like bug@domain.com. A gmail filter receives these emails and forwards them both to the master RTM Inbox address and to a group email that includes all of us.
Whoever is available accesses the master Inbox (usually via Fluid – http://fluidapp.com), tags the new request with bug, feature, etc., and uses "Send To..." to send the task to the appropriate developer's task list, where the recipient can shuffle it into his other tasks, prioritize it, etc. The recipient may also share it with other developers if it's a joint task, and use the notes feature to keep an ongoing record of activity on the issue.
If the developer looking at the master Inbox doesn't know how to deal with a new task, or where to send it, he marks it with priority 3, indicating that it has been looked at but still needs to be looked at by someone else. If someone else then looks at it but doesn't know what to do, he marks it with priority 2, etc. until it makes its way to priority 1, at which time it gets the attention of the next tier of support.
Since RTM is so reliable, we can always refer to the sent list of the master inbox to see all the tasks that came in, where they were sent, etc.
Such a great tool!
Each of us has an RTM account, and there is also a master Inbox account that all developers keep open. We have added each other and the master inbox as contacts in RTM.
We give users an email address like bug@domain.com. A gmail filter receives these emails and forwards them both to the master RTM Inbox address and to a group email that includes all of us.
Whoever is available accesses the master Inbox (usually via Fluid – http://fluidapp.com), tags the new request with bug, feature, etc., and uses "Send To..." to send the task to the appropriate developer's task list, where the recipient can shuffle it into his other tasks, prioritize it, etc. The recipient may also share it with other developers if it's a joint task, and use the notes feature to keep an ongoing record of activity on the issue.
If the developer looking at the master Inbox doesn't know how to deal with a new task, or where to send it, he marks it with priority 3, indicating that it has been looked at but still needs to be looked at by someone else. If someone else then looks at it but doesn't know what to do, he marks it with priority 2, etc. until it makes its way to priority 1, at which time it gets the attention of the next tier of support.
Since RTM is so reliable, we can always refer to the sent list of the master inbox to see all the tasks that came in, where they were sent, etc.
Such a great tool!
Log in
to post a reply.