https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292008-04-26T12:21:44ZRedmineRedmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=24572008-04-26T12:21:44ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Subject</strong> changed from <i>How to create a tracker with all custom fields </i> to <i>Disabling default ticket fields</i></li><li><strong>Category</strong> changed from <i>Custom fields</i> to <i>Issues</i></li><li><strong>Target version</strong> deleted (<del><i>0.7</i></del>)</li></ul><p>Default fields can not be disabled for now.</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=132862009-12-26T15:29:39ZKamil .
<ul></ul><blockquote>
<p>Default fields can not be disabled for now</p>
</blockquote>
<p>Are you going to provide the solution in the future?</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=133432009-12-28T23:36:38ZMischa The Evil
<ul></ul><p>Fixed the issue-relationships...</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=134112010-01-04T08:34:51ZJan Ivar Beddari
<ul></ul><p>Mischa The Evil wrote:</p>
<blockquote>
<p>Fixed the issue-relationships...</p>
</blockquote>
<p>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?</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=134122010-01-04T08:37:19ZJan Ivar Beddari
<ul></ul><p>Sorry, I see now that this is related to <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Configurable required fields per tracker/status/role (Closed)" href="https://www.redmine.org/issues/703">#703</a> and together these are enough. Feel free to remove/delete these non-productive comments :)</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=230552010-12-06T23:01:55Zmythos mint
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=236892011-01-04T22:02:52ZElmer Thomas
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=264122011-03-15T05:40:09ZJames Brown
<ul></ul><p>+1</p>
<p>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.</p>
<p>I am running 1.0.5 and I made the following changes to redmine/app/views/issues/_form.rhtml<br />-------------------------------------------------------------------------------<br />24,26c24,28<br />< <div id="attributes" class="attributes"><br />< <%= render :partial => 'issues/attributes' %><br />< </div><br />---</p>
<blockquote>
<p><% if User.current.roles_for_project(<a class="user active" href="https://www.redmine.org/users/11497">Herve Harster</a>).length != 1 || User.current.roles_for_project(<a class="user active" href="https://www.redmine.org/users/11497">Herve Harster</a>)[0].name != "Reporter" <span>><br /><div id="attributes" class="attributes"><br /><</span>= render :partial => 'issues/attributes' <span>><br /></div><br /><</span> end %></p>
</blockquote>
<hr />
<p>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.<br />It is a quick and VERY dirty hack but it is enough to keep me going until this issue is solved.</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=264572011-03-15T20:06:25ZTerence Mill
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=269182011-03-23T15:22:51ZAmit Ben Shahar
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=277312011-04-08T20:25:33ZDaniel Thornton
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=283072011-04-26T12:42:47ZKurt Hilsmeier
<ul></ul><p>This capability would be huge.</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=283092011-04-26T13:39:51ZTerence Mill
<ul></ul><p>I openeda feature request a time ago, which will include all this kind of field configuration.</p>
<p>See here Issue <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Mightful workflow field enhancement: visible, read only and mandatory (Closed)" href="https://www.redmine.org/issues/8050">#8050</a></p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=310012011-07-22T20:58:27ZJoshua Stein
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=319382011-09-01T13:12:11ZAidin Abedi
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=319602011-09-02T11:30:34ZOlivier Pierard
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=321672011-09-12T16:51:06ZJulien Purjuju
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=327142011-10-06T11:34:44ZChris Lockwood
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=329872011-10-21T13:22:25ZDamien Brugne
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=333642011-10-28T09:52:40ZGurvan Le Dromaguet
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=350432011-12-27T18:19:34ZGlauber Matos
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=351902012-01-05T16:42:53ZSebastián Lara
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=354042012-01-17T13:24:22ZJulien Purjuju
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=370692012-03-27T06:40:17ZRoman E.
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=370802012-03-27T18:55:43ZTerence Mill
<ul></ul><p>duplicate of <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Mightful workflow field enhancement: visible, read only and mandatory (Closed)" href="https://www.redmine.org/issues/8050">#8050</a></p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=378072012-05-01T18:58:36ZRabbit Seagraves
<ul></ul><p>+1</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=379722012-05-06T16:24:03ZBen Flaumenhaft
<ul></ul><p>+1 !!!!!!!!!!</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=389862012-06-13T18:28:53ZLev D
<ul></ul><p>+1 Yes, indeed!</p>
<p>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.</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=394742012-07-05T12:21:09ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>File</strong> <a href="/attachments/7897">standard_fields.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/7897/standard_fields.png">standard_fields.png</a> added</li><li><strong>Subject</strong> changed from <i>Disabling default ticket fields</i> to <i>Disabling default ticket fields per tracker</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Assignee</strong> set to <i>Jean-Philippe Lang</i></li><li><strong>Target version</strong> set to <i>2.1.0</i></li><li><strong>Resolution</strong> set to <i>Fixed</i></li></ul><p>Feature added in <a class="changeset" title="Ability to disable standard fields on a per tracker basis (#1091)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/9912">r9912</a>. You can now disable regular fields on the tracker form:</p>
<p><img src="https://www.redmine.org/attachments/download/7897/standard_fields.png" alt="" /></p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=403232012-08-12T11:34:23ZTerence Mill
<ul></ul><p>That's required in issue <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: per tracker configurable issue form layout with preview (New)" href="https://www.redmine.org/issues/8417">#8417</a></p>
<blockquote>
<p>+1 Yes, indeed!</p>
<p>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.</p>
</blockquote> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=419022012-10-10T10:58:26Zjoseph john
<ul></ul><p>IS this feature also will be enabled on the 1.4 world?</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=420162012-10-15T14:30:22ZBruno Medeiros
<ul></ul><p>joseph john wrote:</p>
<blockquote>
<p>IS this feature also will be enabled on the 1.4 world?</p>
</blockquote>
<p>Sure not.</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=437852013-01-05T03:37:46ZHU an
<ul></ul><p>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...<br />Badly need to need this feature!</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=438002013-01-05T11:25:44ZDaniel Felix
<ul></ul><p>Wan Zhenhuan wrote:</p>
<blockquote>
<p>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...<br />Badly need to need this feature!</p>
</blockquote>
<p>Well, this could be solved after this patch is applied to the core <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Mightful workflow field enhancement: hide (New)" href="https://www.redmine.org/issues/12005">#12005</a>.</p>
<p>Best regards,<br />Daniel</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=509122013-07-31T22:19:06ZMischa The Evil
<ul><li><strong>Precedes</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/14584">Defect #14584</a>: Standard fields disabled for certain trackers still appear in email notifications</i> added</li></ul> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=535662013-12-04T04:37:17ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/12707">Defect #12707</a>: Typo in app/models/tracker.rb</i> added</li></ul> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=589782014-10-04T15:56:45ZDamon Tabb
<ul></ul><p>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.</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=619292015-03-06T03:42:11ZGo MAEDA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/6637">Feature #6637</a>: "unwanted" features as plugins</i> added</li></ul> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=662002015-09-25T11:31:13ZAshish Agrawal
<ul></ul><p>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.</p>
<p>I want standard fields disable options same as custom fields in project settings also.</p> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=765592017-02-09T04:05:23ZGo MAEDA
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/9736">Feature #9736</a>: custom field visibility based on tracker</i> added</li></ul> Redmine - Feature #1091: Disabling default ticket fields per trackerhttps://www.redmine.org/issues/1091?journal_id=851162018-05-21T14:57:55ZGo MAEDA
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/8150">Feature #8150</a>: Suggestion for editing Issue form</i> added</li></ul>