rickbradley's dashboard

I would also really like a copy -- rick@rickbradley.com – rickbradley, on April 23, 2009 14:24

Can this be supported with just a "design" label?

I am also interested in API support (REST, JSON), but integration with other tools is not necessarily high on my list. It's been pretty straightforward to run projects from idea to delivery with Tracker without integrating with anything else. A git or github hook would be nice, but a simple REST/JSON API would make that trivial to implement (i.e., why clutter up the tracker with it?).

To me wiki brainstorming, shared whiteboards, outliners, paper & crayons, etc., are fine if that's what gets the ideas flowing, but ultimately the requirements for development should be specifiable in story format on a 3x5 card.

I'd rather see Tracker get *simpler* in this story collection regard and leave the brainstorming tools for external brainstorming. Be mindful, condense the knowledge into stories and let the other artifacts go. If you still need them, You're Doing It Wrong.

Once the application is launched and customer trouble tickets, bug tracking, etc., are underway, that's a job for a different tool (JIRA, RT, etc.). The relationship between user support tickets and development stories is m:n and I've never seen automated or streamlined flow from support ticket to developer story work well.

Just my opinion, obviously, but turning Tracker into a tool that integrates with user support tools is going to change Tracker for the worse when what is needed is a mindful human to mediate between the world of support and the world of development.

Rick