Feature #1091
Disabling default ticket fields per tracker
| Status: | Closed | Start date: | 2008-04-23 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jean-Philippe Lang | % Done: | 0% | |
| Category: | Issues | |||
| Target version: | 2.1.0 | |||
| Resolution: | Fixed |
Description
I want to create a tracker with all the custom fields. I don't want any default fields to be displayed in it
Related issues
Associated revisions
Ability to disable standard fields on a per tracker basis (#1091).
generate translation files (#1091)
History
#1
Updated by Jean-Philippe Lang over 13 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 . almost 12 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 11 years ago
Fixed the issue-relationships...
#4
Updated by Jan Ivar Beddari over 11 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 11 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 almost 11 years ago
+1
#7
Updated by Elmer Thomas over 10 years ago
+1
#8
Updated by James Brown over 10 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 over 10 years ago
+1
#10
Updated by Amit Ben Shahar over 10 years ago
+1
#11
Updated by Daniel Thornton over 10 years ago
+1
#12
Updated by Kurt Hilsmeier over 10 years ago
This capability would be huge.
#13
Updated by Terence Mill over 10 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 about 10 years ago
+1
#15
Updated by Aidin Abedi about 10 years ago
+1
#16
Updated by Olivier Pierard about 10 years ago
+1
#17
Updated by Julien Purjuju about 10 years ago
+1
#18
Updated by Chris Lockwood almost 10 years ago
+1
#19
Updated by Damien Brugne almost 10 years ago
+1
#20
Updated by Gurvan Le Dromaguet almost 10 years ago
+1
#21
Updated by Glauber Matos almost 10 years ago
+1
#22
Updated by Sebastián Lara over 9 years ago
+1
#23
Updated by Julien Purjuju over 9 years ago
+1
#24
Updated by Roman E. over 9 years ago
+1
#25
Updated by Terence Mill over 9 years ago
duplicate of #8050
#26
Updated by Rabbit Seagraves over 9 years ago
+1
#27
Updated by Ben Flaumenhaft over 9 years ago
+1 !!!!!!!!!!
#28
Updated by Lev D over 9 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 about 9 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 about 9 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 almost 9 years ago
IS this feature also will be enabled on the 1.4 world?
#32
Updated by Bruno Medeiros almost 9 years ago
joseph john wrote:
IS this feature also will be enabled on the 1.4 world?
Sure not.
#33
Updated by HU an over 8 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 8 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 about 8 years ago
- Precedes Defect #14584: Standard fields disabled for certain trackers still appear in email notifications added
#36
Updated by Toshi MARUYAMA almost 8 years ago
- Related to Defect #12707: Typo in app/models/tracker.rb added
#37
Updated by Damon Tabb almost 7 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 over 6 years ago
- Related to Feature #6637: "unwanted" features as plugins added
#39
Updated by Ashish Agrawal about 6 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 4 years ago
- Duplicated by Feature #9736: custom field visibility based on tracker added
#41
Updated by Go MAEDA over 3 years ago
- Duplicated by Feature #8150: Suggestion for editing Issue form added