This is very interesting. We also use Google Docs for stories/specs and Trello for prioritization and roadmap. However, we maintain a separate bug tracker (Open Atrium) for our enterprise clients to report bugs. We'd also love to have a single prioritization list. Wish there was an ability to create a Trello list sync'd with RSS Feed from Open Atrium.
> It’s the product development version of the Hunger Games
Ah, it's worth clarification here. Here's how we use the nomenclature:
Ticket - a message a customer sends in about an issue or question.
Bug - an issue (that can come from any source) which we track and resolve.
We just Trello for bugs (which may be reported in tickets) but we use UserVoice Helpdesk (http://www.uservoice.com/helpdesk) for tickets. Helpdesk is designed around customer communication, Trello is designed around development.
Comments
> Don’t have a separate system for bugs
This is very interesting. We also use Google Docs for stories/specs and Trello for prioritization and roadmap. However, we maintain a separate bug tracker (Open Atrium) for our enterprise clients to report bugs. We'd also love to have a single prioritization list. Wish there was an ability to create a Trello list sync'd with RSS Feed from Open Atrium.
> It’s the product development version of the Hunger Games
:)
Ah, it's worth clarification here. Here's how we use the nomenclature:
Ticket - a message a customer sends in about an issue or question.
Bug - an issue (that can come from any source) which we track and resolve.
We just Trello for bugs (which may be reported in tickets) but we use UserVoice Helpdesk (http://www.uservoice.com/helpdesk) for tickets. Helpdesk is designed around customer communication, Trello is designed around development.
Hope that clarifies! :)