Thumbs WAY up on this request.

I think it would also be great to be able to configure what fields can be seen by what roles. Especially when entering issues. For example, consider the "assigned to" field…

Right now, anyone that can enter an issue can set the "assigned to" field. I would really prefer that "reporter" and "non member" role users not be able to do this.
--------------------------------------------------------------------------------
This issue issue would be AMAZING!!! It is SOOO NEEDED!!!
--------------------------------------------------------------------------------
Completely agree. We have multiple I.T. staff members and when our less-than-technically minded users try and send in tasks, we don't always see them because they don't get assigned. We really want to make Assigned To a required field and I cannot figure out how to do so.

Thanks for this fantastic application, though - it has changed our lives!!
--------------------------------------------------------------------------------
+1

http://www.redmine.org/issues/2708

--------------------------------------------------------------------------------
Any chance of having this feature in 0.9 ?

Configurable required fields like,
# Assigned to:
# Category:
--------------------------------------------------------------------------------
+1 for 0.9
(and where is the voting option by the way?!)
--------------------------------------------------------------------------------
Any body has patch for this? (make "Category:" as required field)

--------------------------------------------------------------------------------
The following patch makes issue category required:

<pre>
Index: app/models/issue.rb
===================================================================
--- app/models/issue.rb (revision 3238)
+++ app/models/issue.rb (working copy)
@@ -48,7 +48,7 @@

DONE_RATIO_OPTIONS = %w(issue_field issue_status)

- validates_presence_of :subject, :priority, :project, :tracker, :author, :status
+ validates_presence_of :subject, :priority, :project, :tracker, :author, :status, :category
validates_length_of :subject, :maximum => 255
validates_inclusion_of :done_ratio, :in => 0..100
validates_numericality_of :estimated_hours, :allow_nil => true
</pre>

--------------------------------------------------------------------------------
Jean-Philippe Lang wrote:
> The following patch makes issue category required:
>
> [...]

JP, Thanks a lot for the patch. It is working fine for new issues, but not for update (System let me blank the category value during update)

Regards,
Nanda

--------------------------------------------------------------------------------
Jean-Philippe Lang wrote:
> The following patch makes issue category required:
>
> [...]

Required field indicator (*) is not showing up.

--------------------------------------------------------------------------------
Added issue-relationship to issue #1091.
--------------------------------------------------------------------------------
+1 I just wanted to say that we need this too (making the assigned-to field required). I hope it's helpful for us add comments to the request, so that you know what the community would like to see in future versions.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
The Jean-Philippe Lang's solution is not suitable for me because there are projects without categories. So not being familiar with ruby I made the patch which simply selects first available category:
<pre>
diff --git a/app/models/issue.rb b/app/models/issue.rb
index 8574a61..f4ebb29 100644
--- a/app/models/issue.rb
+++ b/app/models/issue.rb
@@ -211,15 +211,6 @@ class Issue < ActiveRecord::Base
end

def before_create
- # default category
- if category.nil? && project && project.issue_categories
- project.issue_categories.each do |issue_category|
- if category.nil?
- self.category = issue_category
- end
- end
- end
-
# default assignment based on category
if assigned_to.nil? && category && category.assigned_to
self.assigned_to = category.assigned_to
</pre>

I tried to add 'default' field to category to be able to choose default category, but with no success. Maybe someone could help me to do it?
--------------------------------------------------------------------------------
Paul Voelker wrote:
> Thumbs WAY up on this request.
>
> I think it would also be great to be able to configure what fields can be seen by what roles. Especially when entering issues. For example, consider the "assigned to" field…
>
> Right now, anyone that can enter an issue can set the "assigned to" field. I would really prefer that "reporter" and "non member" role users not be able to do this.

Ditto this for me. We're trying to use this as a helpdesk system as well.
--------------------------------------------------------------------------------
+1
would be very important to have such a right, to dis-/enable fields for the specific roles.
This missing feature is the only reason, i can't use redmine in my company (they don't want the customer/reporter to assign tickets to specific users) :(
--------------------------------------------------------------------------------
Paul Voelker wrote:
> Thumbs WAY up on this request.
>
> I think it would also be great to be able to configure what fields can be seen by what roles. Especially when entering issues. For example, consider the "assigned to" field…
>
> Right now, anyone that can enter an issue can set the "assigned to" field. I would really prefer that "reporter" and "non member" role users not be able to do this.

+1

Very usefull feature. When using as a helpdesk would be really nice to hide some options, in other cases, just don't let the users to update it, not even the requirer.

By the way, after all the issue updates, what does the Redmine team says about this feature?

Thanks,
C.
--------------------------------------------------------------------------------
Added relation to issue #1919 as it might be interesting in the light of the scope of this issues subject.
--------------------------------------------------------------------------------
Think would be nice to be able to do a "fine tuning" on view/change field permissions for roles. And also have a "default permissions settings" feature in the scope of the category, project and overall.

This comment also (or better) applies to issue [[#1919]].

Cheers,
CaioToOn!
--------------------------------------------------------------------------------
We are currently using Redmine for internal project management but I want to open Redmine to our customers. In order to create a new issue, Redmine displays unnecessary non required fields even if we reduces the permissions of the role as much as we can. For example, "assigned to", "Priority", ... are confusing for an external reporter. It would be great to hide/show non required default fields based on user's role.

I have read some comments in the forum and found that this issue was covering that feature. Am I wrong ? If not, does anybody have an idea when this feature will be implemented ? Hope the answer will be "It is already there ..." ;-). Opening Redmine to our customers is part of our "end of year targets".

Regards

Christophe Absil
--------------------------------------------------------------------------------
+1

I am also in the process of (trying) to start using Redmine for bug tracking too. But Issues reports will come more or less from the end user perspective, they do not know which fault it is, how long it will take it to fix it etc.

AFAIK erasing the default field is not possible, maybe one of the following options is more do able:

# option greying them out so the issue reporter can't enter values there
# ignoring them. the issue reporter: values can enter the values, but there will be simply not saved
# informing the issue reporter: this value(s) are/is only a "hint" or a "suggestion"

I hope this import detail issue goes not down in the noise which surround us all.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
p.s. Seriously! This bug is over 3 years old! You know, I did need a good reason to learn Ruby...
--------------------------------------------------------------------------------
+1
One of these long-awaited feature...
--------------------------------------------------------------------------------
+1
I was surprised this feature is not already there. It is very necessary to have the possibility to make fields mandatory/required for us. It is also important that fields can be made invisible for customers. I read in another thread that this also is not possible by now. Please keep these features i track! Thank you
--------------------------------------------------------------------------------
+1 it should be possible to make fields mandatory, optional or hidden on a per tracker-type basis. What apply to some trackers does not apply to all.
--------------------------------------------------------------------------------
This beavhiour is described in _Mightful workflow field enhancement: visible, read only and mandatory_ > #8050

Seth Sandler wrote:
> +1 it should be possible to make fields mandatory, optional or hidden on a per tracker-type basis. What apply to some trackers does not apply to all.

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
In an organization of 6000 people... this feature is absolutely required.

Excellent, excellent product otherwise.
--------------------------------------------------------------------------------
+1
My organization would benefit from this feature request as well. We've had a number of users ask for it.
--------------------------------------------------------------------------------
+1 (unless you count my customers asking for this, then it's +5)
--------------------------------------------------------------------------------
It's very important for to remove default fields just for one tracker. Is a solution exist ?
--------------------------------------------------------------------------------
It's very important for me to remove default fields just for one tracker. Is a solution exist ?
--------------------------------------------------------------------------------
This feature definitely needs to be included in redmine. I've implemented the patch by Jean-Philippe but it didn't add the asterix sign next to the label, here is my updated patch for the *Assignee field*. I hope it helps:

<pre>
Index: app/models/issue.rb
===================================================================
- validates_presence_of :subject, :priority, :project, :tracker, :author, :status
+ validates_presence_of :subject, :priority, :project, :tracker, :author, :status, :assigned_to

Index: app/views/issues/_attributes.rhtml
===================================================================
- f.select :assigned_to_id, (@issue.assignable_users.collect {|m| [m.name, m.id]}), :include_blank => true
+ f.select :assigned_to_id, (@issue.assignable_users.collect {|m| [m.name, m.id]}), :required => true, :include_blank => true
</pre>
--------------------------------------------------------------------------------
+1

this is something very useful to me
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1

I'd like this to be configurable per-project as well, if that wasn't clear from other requests. IE:

project-A - fixed_version is required
project-B - fixed_version is optional (the default)
etc.
--------------------------------------------------------------------------------
Your shall check #8050 , which is more detailed how the requirements can be implemented.
--------------------------------------------------------------------------------
Octavian, thanks for the patch, it works for me. Appreciate it.

Octavian Susnea wrote:
> This feature definitely needs to be included in redmine. I've implemented the patch by Jean-Philippe but it didn't add the asterix sign next to the label, here is my updated patch for the *Assignee field*. I hope it helps:
>
> [...]

--------------------------------------------------------------------------------
+1
Redmine is a great product, but this feature is very important in my company. Would like to have the following default fields configurable as either visible/enabled based on user role:
-Assignee
-Target version
-Priority

Thanks!
--------------------------------------------------------------------------------
How could "this Plugin":https://github.com/resilva/Redmine-Fields-permissions get extended to be able to decided between view/hide, readonly, read/write and mandatory.

*mandatory fields*
<pre>{:required => true} </pre>

*view/hide*
<pre> :disabled </pre>

*readonly*
<pre>??</pre>

Which view has to be pacthed to set rules for user defined fields?
--------------------------------------------------------------------------------
+1

Would be very nice to configure the mandatory default fields.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
Feature added. You can now configure required fields per tracker, status and role.

A new tab is added to the workflow settings to configure required standard/custom fields. This same form is used to configure read-only fields as well (#3521):

!workflow_permissions.png!

Note that if a user has multiple roles on the same project, only fields required for all its roles are actually required.
--------------------------------------------------------------------------------
It's possible add the option Not visible (Required, Read Only and *Not visible*)
--------------------------------------------------------------------------------
Luis Serrano Aranda wrote:
> It's possible add the option Not visible (Required, Read Only and *Not visible*)

+1
Some fields for some roles must be hidden.
--------------------------------------------------------------------------------
Luis Serrano Aranda wrote:
> It's possible add the option Not visible (Required, Read Only and *Not visible*)

*Not Visible* would be a great (and simple?) addition.

Hiding field for all roles is implemented in #1091 but I really would like to hide some fields (Due date, Time spent) for certain roles only.

--------------------------------------------------------------------------------
This will make the feature complete +1
--------------------------------------------------------------------------------
Me too need the feature - hide custom fields per role. But it is must be realized as additional choice - field may be required/readonly and hidden for the clients, for example.

*Jean-Philippe Lang*, what you think?
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
Guys, this ticket is closed. Why don't you create a new one asking for that?
--------------------------------------------------------------------------------
Bruno Medeiros wrote:
> Guys, this ticket is closed. Why don't you create a new one asking for that?

Sorry, recognized the state just after posting... :-(
In future, I will read more intensive the head information, promised! :-)
--------------------------------------------------------------------------------
For people who would come to read the previous comment, it had been done with feature request #5037.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Jean-Philippe Lang wrote:
> Feature added. You can now configure required fields per tracker, status and role.
>
> A new tab is added to the workflow settings to configure required standard/custom fields. This same form is used to configure read-only fields as well (#3521):
>
> !workflow_permissions.png!
>
> Note that if a user has multiple roles on the same project, only fields required for all its roles are actually required.

I am using 2.6-stable branch from Github.

"Required" is not an option for the Subject field.

How can I remove the Subject field, or make it a not required field? Using the above approach my only option is to make it read-only, which is useless.

--------------------------------------------------------------------------------
noah t wrote:
> I am using 2.6-stable branch from Github.
>
> "Required" is not an option for the Subject field.
>
> How can I remove the Subject field, or make it a not required field? Using the above approach my only option is to make it read-only, which is useless.

Do not add note on closed issue with target version.
Please create new issue if you have feature request.
--------------------------------------------------------------------------------
I'm using the 2.6.3 version and I'm not getting permit requirement for standard field.
How can I do this?
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

relates,Closed,2708,Require Category
relates,Closed,1091,Disabling default ticket fields per tracker
relates,Closed,1919,Separate permissions for changing assigned-to, % finished and target version
relates,Closed,8050,Mightful workflow field enhancement: visible, read only and mandatory
relates,Closed,4584,Require a Target Version and Category and provide a default version.
duplicates,Closed,9136,Mandatory Due Date Switch
duplicates,Closed,11055,Conditional mandatory fields
duplicates,Closed,582,Make fields mandatory/unmandatory based on role
duplicates,Closed,2500,configure custom fields as "required for status transition"
duplicates,Closed,1917,Required on close
duplicates,Closed,13336,Custom field option for issues: "required before closed"
duplicates,Closed,10394,Implement permission "Assign users to issues".
duplicates,Closed,514,Custom Field on Closing Screen
duplicates,Closed,4670,Fine tune "New Issue"
duplicates,Closed,16716,Due Date Compulsory