Defect #30771

Author of issue is listed at assignee drop box

Added by VD DV 5 months ago. Updated 4 months ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Permissions and roles
Target version:-
Resolution: Affected version:4.0.0

Description

The issue author that has role with disabled "Issues can be assigned to this role" is still listed at Assignee dropbox (while editing the issue).

1. Role.jpg (88.4 KB) VD DV, 2019-02-08 11:25

2. project_users_and_roles.jpg (77.2 KB) VD DV, 2019-02-08 11:25

3. assigning user that has no rights to be assigned to.jpg (107 KB) VD DV, 2019-02-08 11:25

4. assignment done.jpg (109 KB) VD DV, 2019-02-08 11:25


Related issues

Duplicated by Redmine - Defect #31466: Error assigning a task to a user whose role does not allo... Closed

History

#1 Updated by VD DV 5 months ago

This defect allows to assign issue to user that is not permitted to have issued assigned to him.
Screenshots attached.

#2 Updated by Go MAEDA 5 months ago

The author of an issue is always on the list. I think it is the expected behavior added in r4240.

#3 Updated by VD DV 4 months ago

I think that is not OK. If role does not permit user to have issues assigned to him, the role settings should be respected.

Look at this scenario:
- The reporter (user that should not have issues assigned to him) creates the issue.
- The developer (another user) is assigned through category (as default assigner for that category) of that issue.
- The developer changes status of that issue, and reasigns the issue to the reporter (by chance)
- The reporter updates the issue (the issue that is unfortunately assigned to him),
- That issue remains assigned to reporter after update.

That is wrong, especialy when the reporter have no ability to set assigner (remember that the issue is set through category defined assigner).
Even more serious is that, if reporter updates the issue, no email notification will ever come to initial assigner (developer) to further work on that issue. The developer will never know that issue is lost out of his sight.

Is there possibility to override or disable current unwanted behaviour?

#4 Updated by VD DV 4 months ago

Is there possibility to override or disable current unwanted behaviour?

#5 Updated by Go MAEDA 4 months ago

The behavior may be ”unwanted” for you, but it is not unwanted for other people. Please see #4199.

#6 Updated by VD DV 4 months ago

I agree that some users find that behaviour useful, but some as a defect.
I suppose that it would be nice to have ability to set/unset this functionality on project settings. Maybe you can consider it as a feature.

#7 Updated by Go MAEDA 6 days ago

  • Duplicated by Defect #31466: Error assigning a task to a user whose role does not allow it added

Also available in: Atom PDF