"split" orgs issue permissions into issues and issue management #11998

New Issue

GiteaMirror · 2025-11-02T09:54:00-06:00

GiteaMirror commented

2025-11-02 09:54:00 -06:00

Originally created by @6543 on GitHub (Nov 13, 2023).

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

Originally created by @6543 on GitHub (Nov 13, 2023). 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

GiteaMirror added the type/proposal label 2025-11-02 09:54:00 -06:00

GiteaMirror commented

2025-11-02 09:54:01 -06:00

@lafriks commented on GitHub (Dec 24, 2023):

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

@lafriks commented on GitHub (Dec 24, 2023): But that would issue management levels mean? Just like what issue level admin do?

GiteaMirror commented

2025-11-02 09:54:01 -06:00

@6543 commented on GitHub (Dec 25, 2023):

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 commented on GitHub (Dec 25, 2023): 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

GiteaMirror commented

2025-11-02 09:54:01 -06:00

@6543 commented on GitHub (Dec 25, 2023):

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 :)

@6543 commented on GitHub (Dec 25, 2023): 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 :)

GiteaMirror commented

2025-11-02 09:54:02 -06:00

@lunny commented on GitHub (Dec 27, 2023):

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

@lunny commented on GitHub (Dec 27, 2023): In fact, we have `none`, `read`, `write`, `admin`, `owner`.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#11998

"split" orgs issue permissions into issues and issue management #11998

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