Defect #41439
open
Roles to whom you can not assign an issue - problem when user is Author
Added by Maria Nundahl about 2 months ago.
Updated 16 days ago.
Category:
Permissions and roles
Description
Hi,
I just realized that if the user have a role to whom you can not assign an issue it does not work when the user is the Author of the issue.
To me this must be a defect.
We have a customer role where you are not able to assign an issue to that role. We also have it set up on the role in the workflow so the assignee field is locked for this role.
We are providing support and we do nt want our customers to be able to assign a case to someone and we can not assign the case to the customer.
If someone "by mistake" assign the issue to the Author (our customer) the customer will never be able to assign it back which creates a lot of problem for us.
If the Author of the issue have a role to whom you can not assign a case this should apply to the Author as well.
Is there a set up or fix to this problem?
Please see our Redmine isntallation information:
Files
Any update on this issue?
Can I please get some response on this issue?
When you edit an existing issue, the author of the issue is always listed in the dropdown of the assignee field. This is intended behavior added in r4240.
I recall that we have received several feedback from Redmine users about this behavior.
Should we add a setting like "Allow issue assignment to author regardless of membership and permissions" to disable this behavior?
Yes, a setting like that would solve this problem.
So if you do not turn on this new setting and the author of the case have a role with setting "Issue can be assigned to users with this role" not turned on. Then the Author will not show up in the dropdown list for assignment.
If it would work like that it would be great!
I will open a new issue to propose the feature described in #note-4.
Related issues:
Great, thankyou!
How will I get information if/when the new feature will be available?
Also available in: Atom
PDF