Team with repo.issues = read can create/edit issues #11905

New Issue

GiteaMirror · 2025-11-02T09:51:29-06:00

GiteaMirror commented

2025-11-02 09:51:29 -06:00

Originally created by @YannMagnin on GitHub (Oct 24, 2023).

Description

When accessing a repo as a team member with repo.issues set as read, I can still create and edit issues.

Below is the complete team config (basically I only set repo.code to write and other fields to read):

_STUDENT_TEAM_ACCESS_MAP = {
    "repo.code":        "write",
    "repo.ext_issues":  "none",
    "repo.ext_wiki":    "none",
    "repo.issues":      "read",
    "repo.projects":    "read",
    "repo.pulls":       "read",
    "repo.releases":    "read",
    "repo.packages":    "read",
    "repo.wiki":        "read",
    "repo.actions":     "read",
}

Gitea Version

1.20.5, 1.20.4, 1.20.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Linux Mint, EndeavourOS

How are you running Gitea?

Official binaries, and running from systemd and command-line

Database

None

Originally created by @YannMagnin on GitHub (Oct 24, 2023). ### Description When accessing a repo as a team member with `repo.issues` set as `read`, I can still create and edit issues. Below is the complete team config (basically I only set `repo.code` to `write` and other fields to `read`): ```txt _STUDENT_TEAM_ACCESS_MAP = { "repo.code": "write", "repo.ext_issues": "none", "repo.ext_wiki": "none", "repo.issues": "read", "repo.projects": "read", "repo.pulls": "read", "repo.releases": "read", "repo.packages": "read", "repo.wiki": "read", "repo.actions": "read", } ``` ### Gitea Version 1.20.5, 1.20.4, 1.20.3 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Linux Mint, EndeavourOS ### How are you running Gitea? Official binaries, and running from systemd and command-line ### Database None

GiteaMirror added the issue/needs-feedback label 2025-11-02 09:51:29 -06:00

GiteaMirror closed this issue

2025-11-02 09:51:29 -06:00

GiteaMirror commented

2025-11-02 09:51:30 -06:00

@lunny commented on GitHub (Oct 24, 2023):

This is by design and follow Github.

@lunny commented on GitHub (Oct 24, 2023): This is by design and follow Github.

GiteaMirror commented

2025-11-02 09:51:30 -06:00

@KazzmanK commented on GitHub (Oct 24, 2023):

to follow https://github.com/go-gitea/gitea/issues/26014

@KazzmanK commented on GitHub (Oct 24, 2023): to follow https://github.com/go-gitea/gitea/issues/26014

GiteaMirror commented

2025-11-02 09:51:30 -06:00

@GiteaBot commented on GitHub (Dec 20, 2023):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Dec 20, 2023): We close issues that need feedback from the author if there were no new comments for a month. :tea:

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#11905

Team with repo.issues = read can create/edit issues #11905

Description

Gitea Version

Can you reproduce the bug on the Gitea demo site?

Log Gist

Screenshots

Git Version

Operating System

How are you running Gitea?

Database

Team with `repo.issues = read` can create/edit issues #11905