11–20 of 36 posts
It's a bit basecamp like, but it has a better support for tickets and reports. We moved from basecamp to unfuddle 4 months ago.
And it has an svn repo built in it also which updates your tickets based on your commit comments:
A commit with a message "Closed #44, #45, assign #54 to Joe" does all that in the tickets repository, which helps developers who don't like visiting the management application too much.
If you're a small enough team, you can also get by with a notebook or stickie notes. At my last job I just used a 5x8" spiral notebook, wrote down tasks when my boss asked, and checked them off when I was done.
It's kinda ironic that I've got a more formal process with my one-developer startup than at my last job, but I found that I needed to write lots of little design notes on each feature and cross-reference them as I was implementing. Flipping through pages is a real pain. Plus, it's really satisfying to just say "fixes #11" in a commit message and have the ticket automatically closed.
I'll move to FogBugz eventually.
Trac. If you're a small enough team, you can also get by with a notebook or stickie notes. At my last job I just used a 5x8" spiral notebook, wrote down tasks when my boss asked, and checked them off when I was done. It's kinda ironic that I've got a more formal process with my one-developer startup than at my last job, but I found that I needed to write lots of little design notes on each feature and cross-reference…
We use unfuddle ( http://unfuddle.com/home ) It's a bit basecamp like, but it has a better support for tickets and reports. We moved from basecamp to unfuddle 4 months ago. And it has an svn repo built in it also which updates your tickets based on your commit comments: A commit with a message "Closed #44, #45, assign #54 to Joe" does all that in the tickets repository, which helps developers who don't like visiting…
We're using redmine, http://www.redmine.org/