Redmine

On our projects we like to create very fine-grained issues that sometimes don't need a description. Another use-case is when I just want to scribble down an idea (and maybe fire off an email to redmine from my phone).

Often, we found ourselves either repeating the subject or putting nonsense content into the description field. This quickly got annoying, so I removed that requirement (you can fetch the change from a branch on github). This will reduce the effort to create a ticket, hopefully increasing the number of reported issues and fixed bugs in the process.

A technical requirement like that can never enforce good descriptions as it can always be circumvented. Projects that require a full-blown detailed description with every issue need policies in place and enforce them manually anyway. I think Redmine shouldn't force this on projects that can get by without!

I'd be interested in hearing other opinions.