https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292012-12-19T11:59:36ZRedmineRedmine - Feature #12646: issue relation access managment per tracker and rolehttps://www.redmine.org/issues/12646?journal_id=435422012-12-19T11:59:36ZTerence Mill
<ul></ul><p>!! Please add this to description and change topic to "issue relation access managment per tracker and role"</p>
<p>An example for this stucture looks like follwing.</p>
<pre>
> use case 1
> feature 1
> subtask 1
> subtask 2
> feature 2
> subtask a
> subtask a1
> subtask b
> feature 3
> use case 2
...
..
</pre>
<p>Where use cases have a classified relation (n:n) with features and vice versa. Use cases and deature itself can have subtasks, and subtaks itself. For ressource and project planning the use cases shalle be only createable as the feature and the shall by specila roles. This is possible by worflow already. What still is not possible to restrict is that only special roles are able to create or chnage issue relations where subtask is also a relation line follower, duplicate, blcoked by copied by and so on.</p>
<p>We are missing right based on tracker and role whoc is allowed to create,remove or see this relation per relation type.<br />The mattix would look as folliwng per tracker:</p>
<table>
<tr>
<th>role </th>
<th>copied</th>
<th>dupe</th>
<th>blocked</th>
<th>subtask</th>
<td>..</td>
</tr>
<tr>
<th>developer </th>
<td>dropdown: hide, read,write</td>
<td>dropdown: hide, read,write</td>
<td>dropdown: hide, read,write</td>
<td>dropdown: hide, read,write</td>
<td>..</td>
</tr>
<tr>
<th>tester</th>
<td>dropdown: hide, read,write</td>
<td>dropdown: hide, read,write</td>
<td>dropdown: hide, read,write</td>
<td>dropdown: hide, read,write</td>
<td>..</td>
</tr>
<tr>
<th>manager</th>
<td>dropdown: hide, read,write</td>
<td>dropdown: hide, read,write</td>
<td>dropdown: hide, read,write</td>
<td>dropdown: hide, read,write</td>
<td>..</td>
</tr>
<tr>
<td>..</td>
<td>..</td>
<td>..</td>
<td>..</td>
<td>..</td>
<td>..</td>
</tr>
</table> Redmine - Feature #12646: issue relation access managment per tracker and rolehttps://www.redmine.org/issues/12646?journal_id=435482012-12-19T15:23:36ZDaniel Felix
<ul><li><strong>Subject</strong> changed from <i>allow disallow subtask per tracker</i> to <i>issue relation access managment per tracker and role</i></li></ul> Redmine - Feature #12646: issue relation access managment per tracker and rolehttps://www.redmine.org/issues/12646?journal_id=445232013-01-16T09:23:07ZDaniel Felix
<ul><li><strong>Category</strong> set to <i>Issues permissions</i></li></ul><p>Maybe this could be also introduced with <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>. <br />Your table looks like it could be introduced with some improvements to <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>