Feature #1091
closedDisabling default ticket fields per tracker
Added by girish konnur over 18 years ago. Updated about 11 years ago.
Description
I want to create a tracker with all the custom fields. I don't want any default fields to be displayed in it
Files
| standard_fields.png (6.31 KB) standard_fields.png | Jean-Philippe Lang, 2012-07-05 14:21 |
Updated by Jean-Philippe Lang over 18 years ago
Actions
#1
- 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.
Updated by Kamil . almost 17 years ago
Actions
#2
Default fields can not be disabled for now
Are you going to provide the solution in the future?
Updated by Mischa The Evil almost 17 years ago
Actions
#3
Fixed the issue-relationships...
Updated by Jan Ivar Beddari almost 17 years ago
Actions
#4
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?
Updated by Jan Ivar Beddari almost 17 years ago
Actions
#5
Sorry, I see now that this is related to #703 and together these are enough. Feel free to remove/delete these non-productive comments :)
Updated by mythos mint almost 16 years ago
Actions
#6
+1
Updated by Elmer Thomas almost 16 years ago
Actions
#7
+1
Updated by James Brown over 15 years ago
Actions
#8
+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.
Updated by Terence Mill over 15 years ago
Actions
#9
+1
Updated by Amit Ben Shahar over 15 years ago
Actions
#10
+1
Updated by Daniel Thornton over 15 years ago
Actions
#11
+1
Updated by Kurt Hilsmeier over 15 years ago
Actions
#12
This capability would be huge.
Updated by Terence Mill over 15 years ago
Actions
#13
I openeda feature request a time ago, which will include all this kind of field configuration.
See here Issue #8050
Updated by Joshua Stein over 15 years ago
Actions
#14
+1
Updated by Aidin Abedi about 15 years ago
Actions
#15
+1
Updated by Olivier Pierard about 15 years ago
Actions
#16
+1
Updated by Julien Purjuju about 15 years ago
Actions
#17
+1
Updated by Chris Lockwood about 15 years ago
Actions
#18
+1
Updated by Damien Brugne about 15 years ago
Actions
#19
+1
Updated by Gurvan Le Dromaguet about 15 years ago
Actions
#20
+1
Updated by Glauber Matos almost 15 years ago
Actions
#21
+1
Updated by Sebastián Lara almost 15 years ago
Actions
#22
+1
Updated by Julien Purjuju almost 15 years ago
Actions
#23
+1
Updated by Roman E. over 14 years ago
Actions
#24
+1
Updated by Terence Mill over 14 years ago
Actions
#25
duplicate of #8050
Updated by Rabbit Seagraves over 14 years ago
Actions
#26
+1
Updated by Ben Flaumenhaft over 14 years ago
Actions
#27
+1 !!!!!!!!!!
Updated by Lev D over 14 years ago
Actions
#28
+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.
Updated by Jean-Philippe Lang over 14 years ago
Actions
#29
- File standard_fields.png 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:

Updated by Terence Mill over 14 years ago
Actions
#30
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.
Updated by joseph john about 14 years ago
Actions
#31
IS this feature also will be enabled on the 1.4 world?
Updated by Bruno Medeiros about 14 years ago
Actions
#32
joseph john wrote:
IS this feature also will be enabled on the 1.4 world?
Sure not.
Updated by HU an almost 14 years ago
Actions
#33
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!
Updated by Daniel Felix almost 14 years ago
Actions
#34
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
Updated by Mischa The Evil over 13 years ago
Actions
#35
- Precedes Defect #14584: Standard fields disabled for certain trackers still appear in email notifications added
Updated by Toshi MARUYAMA almost 13 years ago
Actions
#36
- Related to Defect #12707: Typo in app/models/tracker.rb added
Updated by Damon Tabb about 12 years ago
Actions
#37
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.
Updated by Go MAEDA over 11 years ago
Actions
#38
- Related to Feature #6637: "unwanted" features as plugins added
Updated by Ashish Agrawal about 11 years ago
Actions
#39
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.
Updated by Go MAEDA almost 10 years ago
Actions
#40
- Has duplicate Feature #9736: custom field visibility based on tracker added
Updated by Go MAEDA over 8 years ago
Actions
#41
- Has duplicate Feature #8150: Suggestion for editing Issue form added