https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292008-04-08T03:19:03ZRedmineRedmine - Feature #1014: Make issue description non-required fieldhttps://www.redmine.org/issues/1014?journal_id=22042008-04-08T03:19:03ZEric Davis
<ul></ul><p>+1 I tend to copy and paste the subject into the description which is really annoying</p> Redmine - Feature #1014: Make issue description non-required fieldhttps://www.redmine.org/issues/1014?journal_id=26542008-05-07T00:26:39ZEric Davis
<ul><li><strong>File</strong> <a href="/attachments/504">allow_empty_descriptions-1014.diff</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/504/allow_empty_descriptions-1014.diff">allow_empty_descriptions-1014.diff</a> added</li></ul><p>Patch attached with unit test.</p> Redmine - Feature #1014: Make issue description non-required fieldhttps://www.redmine.org/issues/1014?journal_id=26742008-05-08T02:53:50ZHenrique Bastos
<ul><li><strong>File</strong> <a href="/attachments/520">allow_empty_descriptions-1014_2.diff</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/520/allow_empty_descriptions-1014_2.diff">allow_empty_descriptions-1014_2.diff</a> added</li></ul><p>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".<br />Here goes another patch file.</p> Redmine - Feature #1014: Make issue description non-required fieldhttps://www.redmine.org/issues/1014?journal_id=26942008-05-09T08:24:56ZMaxim KruĊĦina
<ul></ul><p>Thank You, Eric. So it seems I have to learn how to deal with .diff files ;)<br />Because we're using SVN to upgrade our Redmine, dosen't create some conflict states after updating SVN when usinf diff'ed files?<br />And why not to use this modification in trunk?<br />Thanx!</p> Redmine - Feature #1014: Make issue description non-required fieldhttps://www.redmine.org/issues/1014?journal_id=26982008-05-09T15:42:23ZEric Davis
<ul></ul><blockquote>
<p>Because we're using SVN to upgrade our Redmine, dosen't create some conflict states after updating SVN when usinf diff'ed files?</p>
</blockquote>
<p>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:</p>
<ol>
<li>Apply patch<br /> <code>patch -p0 < the-patch-file.diff</code></li>
<li>... some time later ...</li>
<li>Reverse the patch<br /> <code>patch -p0 -r < the-patch-file.diff</code></li>
<li>Upgrade SVN copy:<br /> <code>svn update</code></li>
<li>Reapply the patch to the updated code:<br /> <code>patch -p0 < the-patch-file.diff</code></li>
</ol>
<blockquote>
<p>And why not to use this modification in trunk?</p>
</blockquote>
<p>I don't have permissions to commit to SVN directly.</p> Redmine - Feature #1014: Make issue description non-required fieldhttps://www.redmine.org/issues/1014?journal_id=65212009-01-07T23:14:22ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Target version</strong> set to <i>0.9.0</i></li><li><strong>Resolution</strong> set to <i>Fixed</i></li></ul><p>Done in <a class="changeset" title="Makes issue description a non-required field (#2456)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/2246">r2246</a>.</p>