https://it.michalczyk.pro/https://it.michalczyk.pro/favicon.ico?15431677302020-05-12T16:10:44ZIssue trackerIssue recurring - task #26: Plugin doesn't work when you have a recurrence to a bloqued userhttps://it.michalczyk.pro/issues/26?journal_id=882020-05-12T16:10:44Zcryptogopher
<ul><li><strong>Status</strong> changed from <i>new</i> to <i>feedback</i></li><li><strong>Priority</strong> changed from <i>bug</i> to <i>5</i></li></ul><p>Hi, thank you for reporting!</p>
<p>What is a role of the blocked user regarding this issue? Do I understand correctly, that the recurring issue has been assigned to the blocked user?</p>
<p>It would be best if you could provide:<br />a) steps required to reproduce the problem,<br />b) what outcome would you expect instead of error you get (in case the blocked user has been set as an assignee, I think the best plugin could do is to apply default Redmine assignment procedure for new issue; but please let me know what you think).</p> Issue recurring - task #26: Plugin doesn't work when you have a recurrence to a bloqued userhttps://it.michalczyk.pro/issues/26?journal_id=892020-05-15T19:46:15Zcryptogopher
<ul><li><strong>Status</strong> changed from <i>feedback</i> to <i>closed</i></li></ul><p>Fixed in <a class="changeset" title="Added assignee validity check/error logging Improved logging to enable multiple errors in single..." href="https://it.michalczyk.pro/projects/issue-recurring/repository/revisions/93593d4b5d65ccad3ef7965262e370e7a7259a11">93593d4b</a></p>
<p>When previous assignee is no longer assignable (e.g. due to account being blocked or any other reason recognized by Redmine) and keep_assignee setting is used, default Redmine assignment applies and warning is recorded in issue's note.</p>
<p>Fix will be available in earliest release.</p>