Comments on: Managing Projects with Trac http://www.contenthere.net/2006/08/managing-projects-with-trac.html Enter Content Here Wed, 28 Jul 2010 21:53:39 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Seth http://www.contenthere.net/2006/08/managing-projects-with-trac.html/comment-page-1#comment-670 Seth Wed, 18 Jun 2008 18:50:00 +0000 http://www1.contenthere.net/2006/08/managing-projects-with-trac.html#comment-670 I would make a "maintenance" milestone to associate all little fixes with. Then I would also plan around some bigger releases. If you get an issue that turns into something bigger than a quick fix, you would associate it with another (more formal milestone). <br/><br/>I would something like tags (http://trac-hacks.org/wiki/TagsPlugin) for things like "htmlupdate." You could use "components for things like your "about us" section. I would make a “maintenance” milestone to associate all little fixes with. Then I would also plan around some bigger releases. If you get an issue that turns into something bigger than a quick fix, you would associate it with another (more formal milestone).

I would something like tags (http://trac-hacks.org/wiki/TagsPlugin) for things like “htmlupdate.” You could use “components for things like your “about us” section.

]]> By: Anonymous http://www.contenthere.net/2006/08/managing-projects-with-trac.html/comment-page-1#comment-669 Anonymous Wed, 18 Jun 2008 17:35:00 +0000 http://www1.contenthere.net/2006/08/managing-projects-with-trac.html#comment-669 Your post and Nicolaisen's comment have been helpful. I was hoping you could comment on the sort of project that I'm doing, and that Nicolaisen sort of did, too.<br/><br/>I'm trying to use trac to list projects to be done for a Web site. It's all HTML coding and maintenance; no full-scale programming like you describe. (You write it, you test it, you upload, you test again.. that's it.)<br/><br/>So I am planning on making "hierarchical" milestones like "update html" and "update html/about us" "update html/products". I'm pretty wary of making different projects, b/c I'm afraid I'll completely lose track of stuff if I'm trying to keep my eye on multiple trac environments. I really need one master list of tasks.<br/><br/>Helpful comments? Scornful replacement instructions? they're all welcome.<br/><br/>thanks! Your post and Nicolaisen’s comment have been helpful. I was hoping you could comment on the sort of project that I’m doing, and that Nicolaisen sort of did, too.

I’m trying to use trac to list projects to be done for a Web site. It’s all HTML coding and maintenance; no full-scale programming like you describe. (You write it, you test it, you upload, you test again.. that’s it.)

So I am planning on making “hierarchical” milestones like “update html” and “update html/about us” “update html/products”. I’m pretty wary of making different projects, b/c I’m afraid I’ll completely lose track of stuff if I’m trying to keep my eye on multiple trac environments. I really need one master list of tasks.

Helpful comments? Scornful replacement instructions? they’re all welcome.

thanks!

]]> By: Thomas Ferris Nicolaisen http://www.contenthere.net/2006/08/managing-projects-with-trac.html/comment-page-1#comment-506 Thomas Ferris Nicolaisen Sun, 10 Sep 2006 14:35:00 +0000 http://www1.contenthere.net/2006/08/managing-projects-with-trac.html#comment-506 At the place I worked before we were quite into Trac. Actually, all the business goals, projects and processes were managed as tickets! Each friday we would have a meet and talk our way through the ~20 tickets, closing them as we figured them completed, or commenting on others where progress had been made (or not).<br/><br/>Additionally, we had implementation tickets as well. But it was a bit of a drag that Trac didn't support multiple projects (I guess you're supposed to have one Trac installation for each project), so we ended up using one component for each project. Because of this we did not fully make use of the svn view feature, nor the milestones.<br/><br/>At the new place we're into Confluence/Jira, but unfortunately the two have not been properly integrated yet, and they both seem to have weak foothold among my colleagues. Trac has fewer features, but sometimes I miss its simplicity and tight integration of wiki and issues/tickets. At the place I worked before we were quite into Trac. Actually, all the business goals, projects and processes were managed as tickets! Each friday we would have a meet and talk our way through the ~20 tickets, closing them as we figured them completed, or commenting on others where progress had been made (or not).

Additionally, we had implementation tickets as well. But it was a bit of a drag that Trac didn’t support multiple projects (I guess you’re supposed to have one Trac installation for each project), so we ended up using one component for each project. Because of this we did not fully make use of the svn view feature, nor the milestones.

At the new place we’re into Confluence/Jira, but unfortunately the two have not been properly integrated yet, and they both seem to have weak foothold among my colleagues. Trac has fewer features, but sometimes I miss its simplicity and tight integration of wiki and issues/tickets.

]]> By: Zak Greant http://www.contenthere.net/2006/08/managing-projects-with-trac.html/comment-page-1#comment-504 Zak Greant Sat, 02 Sep 2006 07:23:00 +0000 http://www1.contenthere.net/2006/08/managing-projects-with-trac.html#comment-504 I also like Trac a good deal - easy to customize, exceedingly usable and so on.<br/><br/>Just make sure to run it inside of a jail. :)<br/><br/>Cheers!<br/>--zak I also like Trac a good deal – easy to customize, exceedingly usable and so on.

Just make sure to run it inside of a jail. :)

Cheers!
–zak

]]>