https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292007-03-21T04:20:00ZRedmineRedmine - Patch #212: Assign To limited by workflowhttps://www.redmine.org/issues/212?journal_id=4812007-03-21T04:20:00ZAlessio Spadaro
<ul></ul><p>Don't know if it is the right way to do it, but sure is the right<br />thing to do IMHO</p> Redmine - Patch #212: Assign To limited by workflowhttps://www.redmine.org/issues/212?journal_id=4802007-11-11T22:39:00ZBalazs Dan
<ul></ul><p>Hello Jean-Philippe,</p>
<p>I think something similar would be very very useful!<br />Now a user can come into a dead end if he assign the issue to<br />a user who is not involved in the new status. With a similar<br />solution we could avoid it.</p>
<p>I've tested this modification and I had to complete conditions<br />with tracker_id and I had to use @assignable_to in<br />change_status.rhtml. It is working but I'm sure it is not the<br />correct implementation! So I cant submit a patch at the moment.</p>
<p>BR,<br />Balazs</p> Redmine - Patch #212: Assign To limited by workflowhttps://www.redmine.org/issues/212?journal_id=4792007-12-10T08:37:00ZMarcin Gil
<ul></ul><p>There should also be a permission settings that only a user who's<br />currently assigned to a task (+ some manager) can reassign the<br />task.</p>
<p>So that I, as a simple team member, cannot reassign my colleague's<br />ticket and reassign it to someone else.</p> Redmine - Patch #212: Assign To limited by workflowhttps://www.redmine.org/issues/212?journal_id=161782010-04-27T08:13:59ZJoseph M
<ul></ul><p>Is this issue fixed in newer versions? Or could someone please detail the steps to resolve it? I think it is really problematic that the workflow can come to a dead end like this.</p>
<p>Joseph</p> Redmine - Patch #212: Assign To limited by workflowhttps://www.redmine.org/issues/212?journal_id=162112010-04-27T21:42:22ZThomas Pihl
<ul></ul><p>This might depend on how you utilize Redmine. We often assign an issue to someone who cannot change state of it. They will comment the issue and assign it back or to someone else. Since anyone can change the issue, it is not stuck.</p>
<p>But then again, i do like even better workflow control and would not mind some control over the assigned to field (both what it contains and who may change it and to what).</p> Redmine - Patch #212: Assign To limited by workflowhttps://www.redmine.org/issues/212?journal_id=268622011-03-23T10:19:32ZToshi MARUYAMA
<ul><li><strong>Category</strong> set to <i>Issues workflow</i></li></ul> Redmine - Patch #212: Assign To limited by workflowhttps://www.redmine.org/issues/212?journal_id=425712012-10-31T19:35:12ZDaniel Felix
<ul></ul><p>Hey there,</p>
<p>this seems to be solved?</p>
<p>You can define special rights for a user if he is the ticket owner and if he just is assigned to it.</p>
<p>Please correct me if i'm wrong? Otherwise this could be closed?</p> Redmine - Patch #212: Assign To limited by workflowhttps://www.redmine.org/issues/212?journal_id=715252016-06-14T04:43:06ZToshi MARUYAMA
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/71525/diff?detail_id=55586">diff</a>)</li></ul> Redmine - Patch #212: Assign To limited by workflowhttps://www.redmine.org/issues/212?journal_id=715262016-06-14T04:44:12ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-4 priority-default" href="/issues/8313">Feature #8313</a>: Restrict Assignee List by Role</i> added</li></ul> Redmine - Patch #212: Assign To limited by workflowhttps://www.redmine.org/issues/212?journal_id=819902017-11-08T13:29:09ZDipan Mehta
<ul></ul><p>Under a given state of the issue - specific people should only be assigned. For example - when issue moves from development to QA and vice-versa.</p>
<p>However, the possible people who can be assigned should be 'role' based and not individual. Because, if workflow has many state, in each state, we need to add list of people who can be assigned. Further, the when people change, new get added, or some exit the project - you need to do the same exercise all over again.</p>
<p>Thus, the assignment restriction should be 'role' based only. As it is this is currently working in Redmine. Also, multiple roles per person is also permissible making it to create a finer role based assignments.</p>
<p>Should this issue be closed by now?</p> Redmine - Patch #212: Assign To limited by workflowhttps://www.redmine.org/issues/212?journal_id=825262017-12-08T10:30:33ZToshi MARUYAMA
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/82526/diff?detail_id=65230">diff</a>)</li></ul>