Feature #1014
Make issue description non-required field
| Status: | Closed | Start date: | 2008-04-08 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Issues | |||
| Target version: | 0.9.0 | |||
| Resolution: | Fixed |
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...
allow_empty_descriptions-1014.diff
(2.2 kB)
allow_empty_descriptions-1014_2.diff
(2.3 kB)
Related issues
History
#1 Updated by Eric Davis about 4 years ago
+1 I tend to copy and paste the subject into the description which is really annoying
#2 Updated by Eric Davis about 4 years ago
- File allow_empty_descriptions-1014.diff added
Patch attached with unit test.
#3 Updated by Henrique Bastos about 4 years ago
- File allow_empty_descriptions-1014_2.diff added
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.
#4 Updated by Maxim Krušina about 4 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!
#5 Updated by Eric Davis about 4 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.
#6 Updated by Jean-Philippe Lang over 3 years ago
- Status changed from New to Closed
- Target version set to 0.9.0
- Resolution set to Fixed
Done in r2246.