https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292009-06-19T14:44:26ZRedmineRedmine - Feature #3506: Need ability to restrict which role can update/select the target version when updating or submitting an issuehttps://www.redmine.org/issues/3506?journal_id=98412009-06-19T14:44:26ZGabriel Baez
<ul><li><strong>Assignee</strong> set to <i>Jean-Philippe Lang</i></li></ul> Redmine - Feature #3506: Need ability to restrict which role can update/select the target version when updating or submitting an issuehttps://www.redmine.org/issues/3506?journal_id=102102009-07-16T19:14:13ZAndy McKay
<ul></ul><p>I second this. The ability to restrict certain fields to certain user types would be invaluable... esp. when dealing with the target version.</p> Redmine - Feature #3506: Need ability to restrict which role can update/select the target version when updating or submitting an issuehttps://www.redmine.org/issues/3506?journal_id=102132009-07-17T06:12:28ZKirill Ponomarev
<ul></ul><p>+1</p> Redmine - Feature #3506: Need ability to restrict which role can update/select the target version when updating or submitting an issuehttps://www.redmine.org/issues/3506?journal_id=469642013-03-18T15:47:18ZDipan Mehta
<ul></ul><p>The combination of <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> (available under version 2.1.0) and <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> (planned) together will solve this.</p>