https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292015-08-21T11:16:21ZRedmineRedmine - Defect #20583: Setting Category/Version as a required field causes error in projects without categories/versionshttps://www.redmine.org/issues/20583?journal_id=655652015-08-21T11:16:21Zbudo kaiman
<ul></ul><p>I will +1 this as it's annoying to have to create a single category for a project when it's required for another project.<br />Ideally, however, this should be fixed as part of <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Make Projects truly independent of each other (New)" href="https://www.redmine.org/issues/1853">#1853</a> by having the workflow per-project.</p> Redmine - Defect #20583: Setting Category/Version as a required field causes error in projects without categories/versionshttps://www.redmine.org/issues/20583?journal_id=662842015-09-28T14:28:34ZGo MAEDA
<ul></ul><p>The same can be said about the "Target version".</p>
<p>I think that the cause of annoyance is that the user cannot know the field is required before submitting the form because "Category" and "Target version" are hidden when they don't have any value.</p>
<p>I think the solution for this issue is to implement <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Do NOT hide category and version fields on issue form when no category or version is configured (Closed)" href="https://www.redmine.org/issues/18004">#18004</a>. It makes those fields visible at all time, so the user can understand the field is required at a glance whether or not those fields have values.</p> Redmine - Defect #20583: Setting Category/Version as a required field causes error in projects without categories/versionshttps://www.redmine.org/issues/20583?journal_id=665672015-10-10T03:53:17ZGo MAEDA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/18004">Feature #18004</a>: Do NOT hide category and version fields on issue form when no category or version is configured</i> added</li></ul> Redmine - Defect #20583: Setting Category/Version as a required field causes error in projects without categories/versionshttps://www.redmine.org/issues/20583?journal_id=668302015-10-24T06:23:29ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Subject</strong> changed from <i>Setting Category as a required field causes error in projects without categories</i> to <i>Setting Category/Version as a required field causes error in projects without categories/versions</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Assignee</strong> set to <i>Jean-Philippe Lang</i></li><li><strong>Target version</strong> set to <i>3.2.0</i></li><li><strong>Resolution</strong> set to <i>Fixed</i></li></ul><p>Fixed in <a class="changeset" title="Don't require category or target version when they are not available (#20583)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/14733">r14733</a>.</p>