Allow Assignment of Issues to Users with READ access level

[kTitan]

• Gitea version (or commit ref): e87c540
• Git version: 2.17.1
• Operating system: Linux
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

Description

It should be possible to assign issues to people with "read" access.
Currently the users with "read" access rights to a private repo are not shown in the Assignees Dropdown.
But the People can for example send pull requests to the repo. In my opinion it would be logical, if this users can also have issues assigned.

Also Github does have this permission for the "read" access level.
As a reference please look here:
https://help.github.com/articles/repository-permission-levels-for-an-organization/
Line: Have an issue assigned to them

Screenshots

[stevegt]

Does anyone know of a workaround for this? I'd be okay with allowing assignment to any registered user on any repo regardless of collaborator status, for instance. Don't see any way to do that though.

[lunny]

What's permission is reasonable? For a public repository, writers to code and collaborators could be as assigners. For a private repository, readers, writers to code and collaborators could be as assigners.

[kTitan]

That sounds good for me.
In my case the most important part is, that readers of a private repos can become assignees of issues (and of course they still need the permission to create PR)

[lunny]

@kTitan we need a PR to do that.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[stale]

This issue has been automatically closed because of inactivity. You can re-open it if needed.

[stevegt]

Re-opening because still needed afaik.

[davidsvantesson]

I think the required access shall be a setting, at least in app.ini (later on maybe per organization or repo).

To be assignable to an issue or pull request the user shall at least have read access to that unit (doesn't make sense to be assigned to something you can't read).
If you are assigned to an issue/pr you shall be able to make comments in it, even if you only have read access to other issues (comment from @guillep2k)

What options should there be for which are assignable? Some ideas:

• Read access to the issue/pr
• Write access to the issue/pr
• Read access to the issue/pr and write access to some other unit (code or pr?)
• Write access to the issue/pr OR read access when repo admin assign
• Read access but only repo admin can assign

We should make a good consideration which alternatives are really reasonable to avoid complexity in the code.