@pixelmonkey i recently implemented a chef/vagrant deployment to the rackspace cloud. I'm extremely curious how you managed to share the setup between rackspace cloud and local vagrant boxes. I used the vagrant-rackspace plugin, and it seemed like I would need a separate vagrantfile for local vs remote deployments.
The piece thats missing for me with tracker is the conversation. As atomical points out, there are times where you want the story to have some vaguer requirements to allow it to breathe and evolve on its own. During times like these, it grows through the conversation and chair-spin between developers, product owners, etc.
On tracker, the comments system is abysmal, so you either end up with a long unreadable conversation (god forbid there be more than 2 people discussing something at once -- thats a nightmare) that noone wants to read, and thus the curated requirements for the story are missing and would take 30-45 minutes to find.
OR
the comments system is abandoned, and you lose the ability to "track" this part of the process. Epic lose.
Can't wait to see jcooper's work-of-art chrome extension. ;)
I see Tracker as a prioritization tool first and a way to capture stories second. It is highly opinionated about and focused on prioritization but leaves the details of story writing and the conversations apolzon is looking for up to you.
I like this balance and aim for brief story titles with descriptions which include the "As a <role>, I want <goal/desire> so that <benefit>" style requirements, implementation concerns, and other acceptance criteria. I could certainly see a place for a more opinionated story writing tool though. Especially for team who struggle to produce actionable stories.
I also see a Tracker story as a placeholder for a conversation which needs to happen. Not as a good tool for mediating that conversation in the story comments and attachments.
