https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292010-03-12T16:04:17ZRedmineRedmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=151012010-03-12T16:04:17ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Subject</strong> changed from <i>Role-based field visibility</i> to <i>Role-based custom field visibility</i></li></ul> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=155462010-03-30T13:59:56ZGints Murāns
<ul></ul><p>+1 For role based custom fields. This is important, because there is information we as developers don't want to share with everybody else. For example organization heads are not interested in seeing information about technical aspect of the issue?</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=287142011-05-06T17:49:13Zpasquale [:dedalus]
<ul></ul><p>+1</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=287322011-05-08T02:14:42ZTerence Mill
<ul></ul><p>particial dupe of, covered by <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 #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=343272011-11-30T10:52:24ZPanagiotis Korros
<ul></ul><p>+1</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=404282012-08-20T10:24:24ZMoni Ghaoui
<ul></ul><p>+1</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=429432012-11-19T23:05:58ZTerence Mill
<ul></ul><p>related (dupe) of Mightful workflow field enhancement: hide <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> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=441342013-01-12T17:39:03ZDaniel Felix
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Duplicate</i></li></ul><p>Well I'm closing this, even if <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> isn't implemented now. But <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> will resolve exact this request after implementation!<br />Anyway it's kind of duplicate, even if it was an earlier entry than <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> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=496942013-05-28T07:56:24ZErnesto Baschny
<ul></ul><p>+1 on this, would be a nice improvement, and not overly complex.</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=496952013-05-28T07:57:32ZErnesto Baschny
<ul></ul><p>Should not be restricted to "custom fields" of course, but to all fields of an issue.</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=496962013-05-28T08:00:39ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>New</i></li><li><strong>Assignee</strong> set to <i>Jean-Philippe Lang</i></li><li><strong>Target version</strong> set to <i>2.4.0</i></li></ul> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=496982013-05-28T08:18:20ZDavid Robinson
<ul></ul><p>+1</p>
<p>Being able to "hide" certain fields (including not custom fields) for certain roles would be much appreciated.</p>
<p>Also mail updates, reports (pdf) and feeds should not carry hidden fields for the roles for which they have been hidden.</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=497002013-05-28T08:57:13ZVD DV
<ul></ul><p>++++1 for planning this feature for next version. Great!!!</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=497012013-05-28T09:01:42ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><p>David Robinson wrote:</p>
<blockquote>
<p>Being able to "hide" certain fields (including not custom fields) for certain roles would be much appreciated.</p>
</blockquote>
<p>Well, this feature planned for 2.4.0 is about <strong>custom fields</strong> only. Being able to hide some standard fields would be a bit trickier and might be added later, sorry.</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=497022013-05-28T09:09:55ZDavid Robinson
<ul></ul><p>Jean-Philippe Lang wrote:</p>
<blockquote>
<p>David Robinson wrote:</p>
<blockquote>
<p>Being able to "hide" certain fields (including not custom fields) for certain roles would be much appreciated.</p>
</blockquote>
<p>Well, this feature planned for 2.4.0 is about <strong>custom fields</strong> only. Being able to hide some standard fields would be a bit trickier and might be added later, sorry.</p>
</blockquote>
<p>OK, Should I create a new feature request for it then?</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=497052013-05-28T09:11:59ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><p>David Robinson wrote:</p>
<blockquote>
<p>OK, Should I create a new feature request for it then?</p>
</blockquote>
<p>Sure, and thanks for the feedback!</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=497072013-05-28T09:23:21ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul>Here are some details about the possible implementation of custom fields visibility:
<ul>
<li>update the issue custom field form in order to select roles that can see the field</li>
<li>update the issue view (HTML, PDF, API) to hide hidden custom fields, including in the issue history (custom fields changes)</li>
<li>update the issue form to exclude hidden custom fields</li>
<li>completely exclude custom fields from the issue list (columns/filters) if they are not visible by the user on any projects</li>
<li>update the issue list (HTML, PDF, CSV, API) to hide hidden custom fields values per row (on the cross-project list, the user might be able to see custom fields for some projects but not for some other projects, depending on his roles on these projects)</li>
<li>when filtering or grouping the issue list by a custom field, exclude issues for which the custom is not visible</li>
<li>same thing for the time entries list (where issue custom fields can be displayed/filtered)</li>
<li>update the search engine so that it doesn't look up in searchable custom fields that are not visible</li>
<li>update the email notification system so that each user receives an email with only visible custom field (need to change message-ids since multiple emails might now be sent for the same event)</li>
<li>when updating an issue by just changing custom fields values, don't notify users that can't see these custom fields</li>
</ul>
<p>Please let me know if I'm missing something.</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=497082013-05-28T09:34:10ZErnesto Baschny
<ul></ul><p>Jean-Philippe: maybe also consider Custom Queries:</p>
<ul>
<li>don't offer the custom fields that are hidden in "custom queries" (queries/new) "Add filter" option</li>
<li>hide Custom Queries which include filtering by some custom field which is hidden</li>
</ul>
<p>I wonder if it isn't worth to also consider the "regular fields" at the same time, because you will have to touch all those different areas anyway. Or at least prepare an API for it, to make it easier to later hide "regular fields" (maybe someone could then write a plugin to do so).</p>
<p>From the regular fields there are some "special ones" which shouldn't be hideable, i.e. "Status", "Tracker", "Parent Task" and "Subject".</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=497192013-05-28T15:18:15ZToshi MARUYAMA
<ul><li><strong>Resolution</strong> deleted (<del><i>Duplicate</i></del>)</li></ul> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=502592013-06-27T19:22:21ZАлександр Александрук
<ul></ul><p>+1<br />It will be very useful <strong>feature</strong>! Look forward to!<br />Jean-Philippe Lang You're doing a great job, thank you!</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=505262013-07-13T09:32:57ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Subject</strong> changed from <i>Role-based custom field visibility</i> to <i>Role-based issue custom field visibility</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Fixed</i></li></ul><p>Feature added in <a class="changeset" title="Fills locales with new strings." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/12013">r12013</a>. You can now limit the visibility issue custom field to certain roles.</p>
<p>Ernesto Baschny wrote:</p>
<blockquote>
<ul>
<li>don't offer the custom fields that are hidden in "custom queries" (queries/new) "Add filter" option</li>
</ul>
</blockquote>
<p>Done</p>
<blockquote>
<ul>
<li>hide Custom Queries which include filtering by some custom field which is hidden</li>
</ul>
</blockquote>
<p>That would involve too much logic for filtering custom queries. Instead, custom queries can now be made visible to certain roles only (<a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Role based custom queries (Closed)" href="https://www.redmine.org/issues/1019">#1019</a> added for 2.4.0). A user that would be able to display a custom query with fields that are not visible to him wouldn't see them anyway. Queries always take care to show visibile fields only.</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=505302013-07-13T12:33:16ZTerence Mill
<ul></ul><p>This is great Jean! Tx for this.</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=505502013-07-15T08:50:15ZErnesto Baschny
<ul></ul><p>Thanks Jean!</p>
<p>The correct revision where this was added is <a class="changeset" title="Role-based issue custom field visibility (#5037)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/12012">r12012</a>.</p>
<p>Still feature <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> (having the same feature available for standard fields as well) is still very much desired. :)</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=507122013-07-22T21:22:49ZEtienne Massip
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>Reopened</i></li></ul><p>500 when trying to add a spent time custom field to spent time report:</p>
<pre>
ActionView::Template::Error (undefined method `visible_by?' for #<TimeEntryCustomField:0x3e7bb50>):
19: <tbody>
20: <% entries.each do |entry| -%>
21: <tr class="time-entry <%= cycle("odd", "even") %> hascontextmenu">
22: <td class="checkbox hide-when-print"><%= check_box_tag("ids[]", entry.id, false, :id => nil) %></td>
23: <%= raw @query.inline_columns.map {|column| "<td class=\"#{column.css_classes}\">#{column_content(column, entry)}</td>"}.join %>
24: <td align="center">
25: <% if entry.editable_by?(User.current) -%>
app/models/query.rb:84:in `value'
app/helpers/queries_helper.rb:84:in `column_content'
app/views/timelog/_list.html.erb:22:in `block (3 levels) in _app_views_timelog__list_html_erb__1016642981_38612940'
app/views/timelog/_list.html.erb:22:in `map'
app/views/timelog/_list.html.erb:22:in `block (2 levels) in _app_views_timelog__list_html_erb__1016642981_38612940'
app/views/timelog/_list.html.erb:19:in `each'
app/views/timelog/_list.html.erb:19:in `block in _app_views_timelog__list_html_erb__1016642981_38612940'
app/views/timelog/_list.html.erb:1:in `_app_views_timelog__list_html_erb__1016642981_38612940'
app/views/timelog/index.html.erb:20:in `_app_views_timelog_index_html_erb___932575742_45051756'
app/controllers/timelog_controller.rb:64:in `block (2 levels) in index'
app/controllers/timelog_controller.rb:51:in `index'
</pre>
<p><code>CustomField#visible_by?</code> seems to be implemented in <code>IssueCustomField</code> only, did you mean to implement a default one in <code>CustomField</code>?</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=507592013-07-24T18:18:53ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>Reopened</i> to <i>Closed</i></li></ul><p>Etienne Massip wrote:</p>
<blockquote>
<p><code>CustomField#visible_by?</code> seems to be implemented in <code>IssueCustomField</code> only, did you mean to implement a default one in <code>CustomField</code>?</p>
</blockquote>
<p>Thanks for pointing this out, it's fixed in <a class="changeset" title="Fixed that displaying time entries with custom field column raises an error (#5037)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/12041">r12041</a>.</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=508792013-07-30T09:22:43ZVimal Joseph
<ul></ul><p>Thanks for this feature. When can we expect this in a stable release?</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=510442013-08-07T00:17:03ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/3976">Feature #3976</a>: Hide custom fields from certain roles</i> added</li></ul> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=510562013-08-07T07:21:56ZToshi MARUYAMA
<ul><li><strong>Related to</strong> deleted (<i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/3976">Feature #3976</a>: Hide custom fields from certain roles</i>)</li></ul> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=510582013-08-07T07:22:04ZToshi MARUYAMA
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/3976">Feature #3976</a>: Hide custom fields from certain roles</i> added</li></ul> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=520832013-09-26T10:54:56ZSebastian Sp
<ul></ul><p>Hello, is it possible to add this feature to release 2.3.4, as it would be very very nice for our redmine installations.</p>
<p>Best regards,</p>
<p>Sebastian</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=530942013-11-13T08:58:08ZChristoph Klesser
<ul></ul><p>+1</p>
<p>Sebastian Spill wrote:</p>
<blockquote>
<p>Hello, is it possible to add this feature to release 2.3.4, as it would be very very nice for our redmine installations.</p>
<p>Best regards,</p>
<p>Sebastian</p>
</blockquote> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=531002013-11-13T10:05:48ZTobias Fischer
<ul></ul><p>dude, read the ticket! It's planned for the next version 2.4.0!<br />2.3.x releases only contain bugfixes and never any new features...</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=532262013-11-18T19:39:36ZSebastian Sp
<ul></ul><p>Hello,</p>
<p>thanks a lot for quick release! I found a bug regarding this new feature:</p>
<p>When you add custom fields with option "required", the role-based feature does not work correctly. The fields are not displayed, but the validation routine makes the ticket unsaveable.</p>
<p>Regards,</p>
<p>Sebastian</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=532572013-11-19T19:06:37ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><p>Sebastian Spill wrote:</p>
<blockquote>
<p>When you add custom fields with option "required", the role-based feature does not work correctly. The fields are not displayed, but the validation routine makes the ticket unsaveable.</p>
</blockquote>
<p>Please, open a bug report.</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=535372013-12-02T05:15:27ZToshi MARUYAMA
<ul></ul><p>Jean-Philippe Lang wrote:</p>
<blockquote>
<p>Sebastian Spill wrote:</p>
<blockquote>
<p>When you add custom fields with option "required", the role-based feature does not work correctly. The fields are not displayed, but the validation routine makes the ticket unsaveable.</p>
</blockquote>
<p>Please, open a bug report.</p>
</blockquote>
<p>FTR: <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Role-based issue custom field visibility & required field handling (Closed)" href="https://www.redmine.org/issues/15408">#15408</a></p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=546342014-02-03T15:03:29ZStefan T. Oertel
<ul></ul><p>Hi there,</p>
<p>is there a chance to have the feature also for non-issue related custom fields, like "Spent time"? Would be very useful.</p>
<p>Thanks,<br />Stefan</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=575902014-07-17T06:21:40ZJuozapis Juozapauskiksi
<ul><li><strong>File</strong> <a href="/attachments/12014">2014-07-17 09_13_13-Workflow.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/12014/2014-07-17%2009_13_13-Workflow.png">2014-07-17 09_13_13-Workflow.png</a> added</li></ul><p><del>Hi I cannot see any visibility controls. See attached file.</del><br />Sorry looked in wrong place..</p> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=641522015-06-12T06:30:50ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/17096">Defect #17096</a>: Issue emails cannot be threaded by some mailers due to inconsistent Message-ID and References field</i> added</li></ul> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=743312016-11-02T03:00:18ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/23997">Feature #23997</a>: Per role visibility settings for version custom fields</i> added</li></ul> Redmine - Feature #5037: Role-based issue custom field visibilityhttps://www.redmine.org/issues/5037?journal_id=859392018-06-30T06:06:12ZGo MAEDA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-3 status-5 priority-4 priority-default closed" href="/issues/29160">Patch #29160</a>: Remove unused and broken method CustomField.visibility_condition</i> added</li></ul>