Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Admin team's permission is dependent on user selected permissions #4771

Closed
2 of 7 tasks
adelowo opened this issue Aug 23, 2018 · 2 comments
Closed
2 of 7 tasks

Admin team's permission is dependent on user selected permissions #4771

adelowo opened this issue Aug 23, 2018 · 2 comments
Labels

Comments

@adelowo
Copy link
Member

adelowo commented Aug 23, 2018

  • Gitea version (or commit ref): 6ca8fbd
  • Git version: git version 2.15.2 (Apple Git-101.1)
  • Operating system: MacOS
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

STEPS :

  • Create new team

  • In permissions, choose any of read and write, then untick code, issues, pull requests .

  • Then choose Administrator access in permissions

  • Then Update settings

  • Add a repository to the team,

  • Add a non admin user to the team

  • Access the repository, The user would not have any of the unticked permissions earlier even though he is in a team with admin access. ( for instance, he cannot view issues, PRs )

I would expect that the admin team gets all available permissions regardless of the selection(s)

@lunny
Copy link
Member

lunny commented Oct 26, 2018

admin Team should have write permissions of all the units on the repositories of the organization.

@lunny
Copy link
Member

lunny commented Nov 28, 2018

should be fixed by #5314 , close now and please feel free to reopen.

@lunny lunny closed this as completed Nov 28, 2018
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants