What permission is required to allow issues to be assigned to project member ?
Hi,
Let we've an external project's member (not a developer) which we cannot allow to work with codebase (read, write, commit is not allowed).
'Project issues: Edit issue' permission is granted to a role (created new one) of that person. However we still cannot assign issues to that person (not appear in list to assign). What permission is required to present in that list ?
Please sign in to leave a comment.
Hi Sergei, basically, creating a separate role and granting the "Edit issue" permission only should've done the trick, and it's not yet clear what when wrong in your case. To start with, may I ask you to submit a support request, providing the screenshots with the group permissions?
Hi Pavel,
Today, we experimentally found out that person should have pre-defined 'Project member' role to be assignable. So we removed all permissions from 'project member' and added that new person to that role (so effectively person should not be granted with any new permission), and the person appeared in the list for assignment.
This workaround works but made very hard to think about security concerns - if just 'have a role (with no permission)' enable/disable something it must be very clearly described.
I filled a ticket about that. Seems like a bug for me.
Even if it's not a bug, it should be different.