Feature #1014

Make issue description non-required field

Added by Maxim Krušina over 10 years ago. Updated almost 10 years ago.

Status:ClosedStart date:2008-04-08
Priority:NormalDue 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 Magnifier (2.17 KB) Eric Davis, 2008-05-07 02:26

allow_empty_descriptions-1014_2.diff Magnifier (2.29 KB) Henrique Bastos, 2008-05-08 04:53


Related issues

Related to Redmine - Patch #2456: Dont require a Description for every issue Closed 2009-01-07

History

#1 Updated by Eric Davis over 10 years ago

+1 I tend to copy and paste the subject into the description which is really annoying

#2 Updated by Eric Davis over 10 years ago

Patch attached with unit test.

#3 Updated by Henrique Bastos over 10 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.

#4 Updated by Maxim Krušina over 10 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 over 10 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:

  1. Apply patch
    patch -p0 < the-patch-file.diff
  2. ... some time later ...
  3. Reverse the patch
    patch -p0 -r < the-patch-file.diff
  4. Upgrade SVN copy:
    svn update
  5. 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 almost 10 years ago

  • Status changed from New to Closed
  • Target version set to 0.9.0
  • Resolution set to Fixed

Done in r2246.

Also available in: Atom PDF