"split" orgs issue permissions into `issues` and `issue management`

[6543]

right now you can only assign users to repos and they at lest have the right to create issues.

if you want them to let issues see but not create new one there is no option.

so i propose to split up the permission "issues" to "issue management" witch addresses assigning labels ... eg. (what we understand as issue-write-permissions) and "issues" witch default to write witch means create issues

[lafriks]

But that would issue management levels mean? Just like what issue level admin do?

[6543]

admin -> can delete issues too?

we have:

• read (see) issues
• create issues
• change own issues (edit title& desc)
• change other issues (edit title & desc)
• close/re-open own issues
• close/re-open other issues
• delete issues

and we have to create a permission framework to allow/deny this things

[6543]

we currently have "no", "read" and "write" access ... so how we name it and how we split it out i dont know. But if someone compe up with nice name(s) and how to cover mentioned permissions, I'm all for it :)

[lunny]

In fact, we have none, read, write, admin, owner.