Aaron Sumner

Returing to Redmine: Suggestions for better workflows and productivity

cover After experimenting with a number of issue tracking methods (some I’d label antimethods) and products I’ve returned to Redmine for both team-oriented and solo projects. Out of the box, Redmine is a good fit for me in a number of ways:

That said, a fresh installation of Redmine is likely going to need some tweaks before it can help you effectively track issues and products. In my case, I wanted it to be as easy as possible to record an issue and get back to whatever is the task at hand. As anyone who’s installed Redmine and poked around its settings can tell, the software itself is pretty flexible. The trick is knowing how to make those settings work with your workflow.

To do this, I strongly recommend Eric Davis’ e-book Redmine Tips. As both a core Redmine developer and daily user of the software, Eric does a good job walking through not just how to adjust Redmine’s settings, but also good reasons why to adjust them in certain ways.

After going through the tips in the book I did the following:

A few more suggestions:

Redmine for non-technical projects?

My next step is to explore Redmine’s possibilities as a management tool for non-software projects—specifically, proposal writing and instructional design. If you have experience with using Redmine or a similar product outside of typical technical products I’d love to hear from you.

. Questions or comments? Let me know what you think.