Feature #1091: Disabling default ticket fields per tracker - Redmine

#1 Updated by Jean-Philippe Lang about 11 years ago

Subject changed from How to create a tracker with all custom fields to Disabling default ticket fields
Category changed from Custom fields to Issues
Target version deleted (~~0.7~~)

Default fields can not be disabled for now.

#2 Updated by Kamil . over 9 years ago

Default fields can not be disabled for now

Are you going to provide the solution in the future?

#3 Updated by Mischa The Evil over 9 years ago

Fixed the issue-relationships...

#4 Updated by Jan Ivar Beddari over 9 years ago

Mischa The Evil wrote:

Fixed the issue-relationships...

Mischa, how about changing or adding to the title of this feature so that it describes the ones it duplicates also, more accurately.. ? I'm thinking a solution to this is more general than disabling the default ticket fields?

#5 Updated by Jan Ivar Beddari over 9 years ago

Sorry, I see now that this is related to #703 and together these are enough. Feel free to remove/delete these non-productive comments :)

#6 Updated by mythos mint over 8 years ago

+1

#7 Updated by Elmer Thomas over 8 years ago

+1

#8 Updated by James Brown about 8 years ago

+1

I need to have a new issues interface that can be used by external parties. I don't want them to be able to see the "Assigned to" or "Due date" etc fields.

I am running 1.0.5 and I made the following changes to redmine/app/views/issues/_form.rhtml
-------------------------------------------------------------------------------
24,26c24,28
< <div id="attributes" class="attributes">
< <%= render :partial => 'issues/attributes' %>
< </div>
---

<% if User.current.roles_for_project(@project).length != 1 || User.current.roles_for_project(@project)[0].name != "Reporter" >
<div id="attributes" class="attributes">
<= render :partial => 'issues/attributes' >
</div>
< end %>

This will render the issue attributes IF AND ONLY IF the user is a "Reporter" role. This will also remove access to any custom fields.
It is a quick and VERY dirty hack but it is enough to keep me going until this issue is solved.

#9 Updated by Terence Mill about 8 years ago

+1

#10 Updated by Amit Ben Shahar about 8 years ago

+1

#11 Updated by Daniel Thornton about 8 years ago

+1

#12 Updated by Kurt Hilsmeier about 8 years ago

This capability would be huge.

#13 Updated by Terence Mill about 8 years ago

I openeda feature request a time ago, which will include all this kind of field configuration.

See here Issue #8050

#14 Updated by Joshua Stein almost 8 years ago

+1

#15 Updated by Aidin Abedi over 7 years ago

+1

#16 Updated by Olivier Pierard over 7 years ago

+1

#17 Updated by Julien Purjuju over 7 years ago

+1

#18 Updated by Chris Lockwood over 7 years ago

+1

#19 Updated by Damien Brugne over 7 years ago

+1

#20 Updated by Gurvan Le Dromaguet over 7 years ago

+1

#21 Updated by Glauber Matos over 7 years ago

+1

#22 Updated by Sebastián Lara over 7 years ago

+1

#23 Updated by Julien Purjuju over 7 years ago

+1

#24 Updated by Roman E. about 7 years ago

+1

#25 Updated by Terence Mill about 7 years ago

duplicate of #8050

#26 Updated by Rabbit Seagraves about 7 years ago

+1

#27 Updated by Ben Flaumenhaft about 7 years ago

+1 !!!!!!!!!!

#28 Updated by Lev D almost 7 years ago

+1 Yes, indeed!

No reason not to include this feature. Arranging the form to your liking would also be quite useful. Right now, I added 4 extra fields and my eyes are already jumping around the form looking for the the ones I need to fill in and for those I want to skip.

#29 Updated by Jean-Philippe Lang almost 7 years ago

File standard_fields.png added
Subject changed from Disabling default ticket fields to Disabling default ticket fields per tracker
Status changed from New to Closed
Assignee set to Jean-Philippe Lang
Target version set to 2.1.0
Resolution set to Fixed

Feature added in r9912. You can now disable regular fields on the tracker form:

#30 Updated by Terence Mill almost 7 years ago

That's required in issue #8417

+1 Yes, indeed!

No reason not to include this feature. Arranging the form to your liking would also be quite useful. Right now, I added 4 extra fields and my eyes are already jumping around the form looking for the the ones I need to fill in and for those I want to skip.

#31 Updated by joseph john over 6 years ago

IS this feature also will be enabled on the 1.4 world?

#32 Updated by Bruno Medeiros over 6 years ago

joseph john wrote:

IS this feature also will be enabled on the 1.4 world?

Sure not.

#33 Updated by Wan Zhenhuan over 6 years ago

Why do I still can't disable the "Status/Priority/File attaching/Watchers" field? People wanna add a complete new issue tracker things like meeting/billing/sales...
Badly need to need this feature!

#34 Updated by Daniel Felix over 6 years ago

Wan Zhenhuan wrote:

Why do I still can't disable the "Status/Priority/File attaching/Watchers" field? People wanna add a complete new issue tracker things like meeting/billing/sales...
Badly need to need this feature!

Well, this could be solved after this patch is applied to the core #12005.

Best regards,
Daniel

#35 Updated by Mischa The Evil almost 6 years ago

Precedes Defect #14584: Standard fields disabled for certain trackers still appear in email notifications added

#36 Updated by Toshi MARUYAMA over 5 years ago

Related to Defect #12707: Typo in app/models/tracker.rb added

#37 Updated by Damon Tabb over 4 years ago

But the "priority" field still seems permanent. Is there a way to include that in the list of default fields that can be disabled? I have a specific tracker that doesn't need this field and it's causing some mild confusion with issue reporters.

#38 Updated by Go MAEDA about 4 years ago

Related to Feature #6637: "unwanted" features as plugins added

#39 Updated by Ashish Agrawal over 3 years ago

Is there a plugin to disable the Issue core fields such as assigned_to_id on a project level basis? As per the existing settings, only custom fields can be disabled on a per project basis. Standard fields can be disabled per tracker/role/user but not per project.

I want standard fields disable options same as custom fields in project settings also.

#40 Updated by Go MAEDA over 2 years ago

Duplicated by Feature #9736: custom field visibility based on tracker added

#41 Updated by Go MAEDA 12 months ago

Duplicated by Feature #8150: Suggestion for editing Issue form added

Related to Redmine - Feature #703: Configurable required fields per tracker/status/role	Closed	2008-02-21
Related to Redmine - Feature #9700: Allow to configure the visibility of the fields of the “N...	Closed
Related to Redmine - Defect #12707: Typo in app/models/tracker.rb	Closed
Related to Redmine - Feature #6637: "unwanted" features as plugins	Closed	2010-10-12
Duplicated by Redmine - Feature #4434: Hide target version in ticket mask	Closed	2009-12-17
Duplicated by Redmine - Feature #4387: Managing "description" field	Closed	2009-12-11
Duplicated by Redmine - Feature #1296: Allow trackers to hide issue fields	Closed	2008-05-25
Duplicated by Redmine - Feature #3737: Enabling to Remove Default Fields in New Project Creation	Closed	2009-08-14
Duplicated by Redmine - Feature #3154: Remove default fields on new issue form	Closed	2009-04-10
Duplicated by Redmine - Feature #5032: Ability to remove "Assigned to" field from particular tra...	Closed	2010-03-10
Duplicated by Redmine - Feature #9736: custom field visibility based on tracker	Closed
Duplicated by Redmine - Feature #8150: Suggestion for editing Issue form	Closed	2011-04-14
Precedes Redmine - Defect #14584: Standard fields disabled for certain trackers still appea...	Closed

Redmine

Issues

Custom queries

Feature #1091

Disabling default ticket fields per tracker

Associated revisions

History