Patch #2456
closed
Dont require a Description for every issue
0%
Description
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.
Related issues
Updated by Jack Christensen over 15 years ago
+1
I find myself putting a period in as a filler description on a lot of issues.
Updated by Maxim Krušina over 15 years ago
+10 please, definitly create option to set description field like optinoal... i'm filling nonsence here moe that 10x per day ;)
imho, it can be turned on/off id global config
Updated by Jean-Philippe Lang over 15 years ago
- Category set to Issues
- Status changed from New to Closed
- Target version set to 0.9.0
Change done in r2246. Description is no longer a required field.
IMHO, a setting to turn on/off this behaviour is not that usefull.
Updated by Ewan Makepeace over 15 years ago
+1
Have not seen a good enough reason to upgrade for 5 months or so - but this change is worth upgrading to trunk for :-)
Updated by Jean-Philippe Lang about 15 years ago
- Target version changed from 0.9.0 to 0.8.1