Feature #1014
closed
Make issue description non-required field
0%
Description
Maybe others will no agree with me, but lot of issues I create is filed with "x" or simillar balast in description field, because sometimes I'm deadly descriptive with Subject only ;)
Or, it can be put into Redmine's main configuration so admin will decide if Description is required or not...
Files
Related issues
Updated by Eric Davis about 16 years ago
+1 I tend to copy and paste the subject into the description which is really annoying
Updated by Eric Davis almost 16 years ago
Patch attached with unit test.
Updated by Henrique Bastos almost 16 years ago
Changes seems to work fine, however the patch file has some "git references" and I couldn't just "cd trunk" then "patch -p0 < allow_empty_descriptions-1014.diff".
Here goes another patch file.
Updated by Maxim Krušina almost 16 years ago
Thank You, Eric. So it seems I have to learn how to deal with .diff files ;)
Because we're using SVN to upgrade our Redmine, dosen't create some conflict states after updating SVN when usinf diff'ed files?
And why not to use this modification in trunk?
Thanx!
Updated by Eric Davis almost 16 years ago
Because we're using SVN to upgrade our Redmine, dosen't create some conflict states after updating SVN when usinf diff'ed files?
It shouldn't create a conflict unless the same files where modified in SVN. You can also back out any patches before upgrading by following these steps:
- Apply patch
patch -p0 < the-patch-file.diff - ... some time later ...
- Reverse the patch
patch -p0 -r < the-patch-file.diff - Upgrade SVN copy:
svn update - Reapply the patch to the updated code:
patch -p0 < the-patch-file.diff
And why not to use this modification in trunk?
I don't have permissions to commit to SVN directly.
Updated by Jean-Philippe Lang over 15 years ago
- Status changed from New to Closed
- Target version set to 0.9.0
- Resolution set to Fixed
Done in r2246.