https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292009-02-10T22:05:24ZRedmineRedmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=72502009-02-10T22:05:24ZEric Davis
<ul></ul><p>I don't use categories that much so if this feature is implemented, making category required should be an optional setting.</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=76042009-02-24T14:23:35ZNanda P
<ul></ul><p>+1</p>
<p>We have 10+ Projects. For one of project, the manager wants category field as Required.</p>
<p>As Brandon said "When users submit a ticket, they forget to fill the category out". It is time consuming to go through the description of those tickets & fill the category later.</p>
<p>Another idea: If we can take out the Category field. I can add a custom field called category ;) & make it Required.</p>
<p>I am looking for a temp fix, until we find a solution.</p>
<p>Any suggestions?</p>
<p>Thanks,<br />Nanda</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=85832009-04-09T15:17:19ZPeter Edstrom
<ul></ul><p>+1</p>
<p>See also <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Configurable required fields per tracker/status/role (Closed)" href="https://www.redmine.org/issues/703">#703</a> and <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Make fields mandatory/unmandatory based on role (Closed)" href="https://www.redmine.org/issues/582">#582</a> for slightly different takes on this.</p>
<p>We use inbound email, where a category can be defaulted. This is great because the owner of the category is alerted when a new issue is created. When issues are created in the tool, however, the category is not required and thus no one is guaranteed to be notified of the new issue.</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=86892009-04-17T19:09:04ZNanda P
<ul><li><strong>File</strong> <a href="/attachments/1892">_form.rhtml</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/1892/_form.rhtml">_form.rhtml</a> added</li><li><strong>File</strong> <a href="/attachments/1893">issue.rb</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/1893/issue.rb">issue.rb</a> added</li></ul><p>app\views\issues\_form.rhtml -> Change in line # 27<br /><pre>
validates_presence_of :subject, :description, :priority, :category, :project, :tracker, :author, :status
</pre></p>
<p>app\models\issue.rb -> Change in line # 48<br /><pre>
validates_presence_of :subject, :description, :priority, :category, :project, :tracker, :author, :status
</pre></p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=86902009-04-17T19:10:37ZNanda P
<ul></ul><p>Nanda Palaniswamy wrote:</p>
<blockquote>
<p>appviewsissues_form.rhtml -> Change in line # 27<br />[...]</p>
<p>appmodelsissue.rb -> Change in line # 48<br />[...]</p>
</blockquote>
<p>I modified the above files to make the category as Required field.</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=95772009-06-04T16:57:56ZPaul Voelker
<ul></ul><p>I think giving the option to require the category field would be fantastic. This would be great for those who make use of the auto-assignment functionality of categories.</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=99682009-06-30T14:51:29ZBrandon Dixon
<ul><li><strong>File</strong> <a href="/attachments/2266">_form.rhtml</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2266/_form.rhtml">_form.rhtml</a> added</li></ul><p>I am running the latest version (0.8.4) and it looks like some things were changed.</p>
<p>This works:<br />app\models\issue.rb -> Change in line # 48<br /><pre>
validates_presence_of :subject, :description, :priority, :category, :project, :tracker, :author, :status
</pre></p>
<p>The first mod to the form on the other hand does not work. It now looks like this:<br />app\views\issues\_form.rhtml -> Change in line # 28<br /><pre>
<p><%= f.select :category_id, (@project.issue_categories.collect {|c| [c.name, c.id]}), :include_blank => true, :required => true %>
</pre></p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=128002009-12-08T03:59:57ZNanda P
<ul></ul><p>Brandon,</p>
<p>The patch is not working with trunk version (Redmine 0.8.7.devel.3131)</p>
<p>When you get a chance could you please have a look?</p>
<p>Thanks in Advance<br />Nanda</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=138602010-01-27T18:11:02ZNanda P
<ul></ul><p>Any update on this?</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=178642010-06-30T18:25:49ZJeremy Walker
<ul></ul><p>+1</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=187752010-07-28T15:11:03ZChad S
<ul></ul><p>I have a fix for this guys that works with 1.0.x (which i assume would work with 0.9.x, but i have not tested it.)</p>
<p>Follow it as you normally would with one exception...<br />The edit to this file....:<br />app/views/issues/_form.rhtml<br />should instead be done to this file:<br />app/views/issues/_attributes.rhtml</p>
<p>I have this working after upgrading from 0.8.x to 1.0.x. Reply here if you need help getting this working.</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=206262010-09-23T09:27:22ZPatrick Sherman
<ul></ul><p>+1</p>
<p>Chad, how did you do?</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=215522010-10-19T17:04:34ZAnonymous
<ul></ul><p>How about extending required yes/no to all fields in an issue?<br />Some of them are already required on system level.<br />Given the fact that you can set required yes/no on custom fields, this seems like a logical step.</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=215632010-10-19T19:54:39ZTerence Mill
<ul></ul><p>Even better would be setting required fields dependent on the status for the ticket. This way someone can better design details of the workflow..</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=319682011-09-02T18:20:03ZNathanael Hansen
<ul></ul><p>+1</p> Redmine - Feature #2708: Require Categoryhttps://www.redmine.org/issues/2708?journal_id=323732011-09-20T12:11:17ZEtienne Massip
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Duplicate</i></li></ul><p>Dup of <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Configurable required fields per tracker/status/role (Closed)" href="https://www.redmine.org/issues/703">#703</a>.</p>