Feature #2708: Require Category - Redmine

Custom queries

Documentation issues
Open defects
Open features
Patch queue
Plugin issues
Translation patches

Actions

Copy link

Feature #2708

closed

Require Category

Added by Brandon Dixon almost 16 years ago. Updated over 13 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

2009-02-10

Due date:

% Done:

Estimated time:

Resolution:

Duplicate

Description

As of now I am using Redmine to monitor corporate IT. I have one main project and multiple sub-projects (i.e networking, software, etc.) that users can post tickets to. The problem I have with this is that it doesn't seem like its a correct way of doing things. I would like to have one project and then have users assign their tickets to categories (i.e networking, software, etc.). The problem now is that users submit a ticket, but since its a category is not required users won't always fill it out. This leaves me going back and fixing the mistakes. Is there a way to make the Category value required?

Files

Download all files

_form.rhtml (3.11 KB) _form.rhtml	app\views\issues\_form.rhtml	Nanda P, 2009-04-17 21:09
issue.rb (11.5 KB) issue.rb		Nanda P, 2009-04-17 21:09
_form.rhtml (3.16 KB) _form.rhtml		Brandon Dixon, 2009-06-30 16:51

Related issues

Related to Redmine - Feature #703: Configurable required fields per tracker/status/role

Closed

Jean-Philippe Lang

2008-02-21

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Eric Davis almost 16 years ago

I don't use categories that much so if this feature is implemented, making category required should be an optional setting.

Actions

Copy link

Updated by Nanda P almost 16 years ago

We have 10+ Projects. For one of project, the manager wants category field as Required.

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.

Another idea: If we can take out the Category field. I can add a custom field called category ;) & make it Required.

I am looking for a temp fix, until we find a solution.

Any suggestions?

Thanks,
Nanda

Actions

Copy link

Updated by Peter Edstrom over 15 years ago

See also #703 and #582 for slightly different takes on this.

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.

Actions

Copy link

Updated by Nanda P over 15 years ago

File _form.rhtml _form.rhtml added
File issue.rb issue.rb added

app\views\issues\_form.rhtml -> Change in line # 27

validates_presence_of :subject, :description, :priority, :category, :project, :tracker, :author, :status

app\models\issue.rb -> Change in line # 48

validates_presence_of :subject, :description, :priority, :category, :project, :tracker, :author, :status

Actions

Copy link

Updated by Nanda P over 15 years ago

Nanda Palaniswamy wrote:

appviewsissues_form.rhtml -> Change in line # 27
[...]

appmodelsissue.rb -> Change in line # 48
[...]

I modified the above files to make the category as Required field.

Actions

Copy link

Updated by Paul Voelker over 15 years ago

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.

Actions

Copy link

Updated by Brandon Dixon over 15 years ago

File _form.rhtml _form.rhtml added

I am running the latest version (0.8.4) and it looks like some things were changed.

This works:
app\models\issue.rb -> Change in line # 48

validates_presence_of :subject, :description, :priority, :category, :project, :tracker, :author, :status

The first mod to the form on the other hand does not work. It now looks like this:
app\views\issues\_form.rhtml -> Change in line # 28

<p><%= f.select :category_id, (@project.issue_categories.collect {|c| [c.name, c.id]}), :include_blank => true, :required => true %>

Actions

Copy link

Updated by Nanda P about 15 years ago

Brandon,

The patch is not working with trunk version (Redmine 0.8.7.devel.3131)

When you get a chance could you please have a look?

Thanks in Advance
Nanda

Actions

Copy link

Updated by Nanda P almost 15 years ago

Any update on this?

Actions

Copy link

#10

Updated by Jeremy Walker over 14 years ago

Actions

Copy link

#11

Updated by Chad S over 14 years ago

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.)

Follow it as you normally would with one exception...
The edit to this file....:
app/views/issues/_form.rhtml
should instead be done to this file:
app/views/issues/_attributes.rhtml

I have this working after upgrading from 0.8.x to 1.0.x. Reply here if you need help getting this working.

Actions

Copy link

#12

Updated by Patrick Sherman about 14 years ago

Chad, how did you do?

Actions

Copy link

#13

Updated by Anonymous about 14 years ago

How about extending required yes/no to all fields in an issue?
Some of them are already required on system level.
Given the fact that you can set required yes/no on custom fields, this seems like a logical step.

Actions

Copy link

#14