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

Members of an organization cannot open a private repository (owned by the organization) #2686

Closed
2 of 7 tasks
nardhar opened this issue Oct 11, 2017 · 2 comments
Closed
2 of 7 tasks
Labels
issue/duplicate The issue has already been reported.

Comments

@nardhar
Copy link

nardhar commented Oct 11, 2017

  • Gitea version (or commit ref): 1.2.0
  • Git version: 1.8.3.1
  • Operating system: Centos 7
  • 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

  1. Fresh installed Gitea
  2. Created three users: SampleOwner, SampleCollab, SampleExternal
  3. Logged as SampleOwner
  4. Created an organization SampleOrganization and added SampleCollab as a member
  5. Created a private repository and set SampleOrganization as owner
  6. Logged as SampleCollab and can view the repo in the explore tab, but gets a 404 page when tries to open it

Apparently the problem is that it does not add the SampleCollab user as a collaborator since it is a member of the owner organization, I guess it should be allowed to be added nevertheless, I'll investigate more and post more details about this

Thks in advance

@daviian
Copy link
Member

daviian commented Oct 11, 2017

A member needs to be in a team to have sufficient access rights to repositories.
We have already discussed removing the add member option from UI as it causes confusion and troubles.

Duplicate from #2562, #2593, #1794 and closely related to #2399

@lunny lunny added the issue/duplicate The issue has already been reported. label Oct 11, 2017
@lunny lunny closed this as completed Oct 11, 2017
@nardhar
Copy link
Author

nardhar commented Oct 11, 2017

having a team as owner works perfectly, but I expected that an organization would work the same, guess I will take the team approach as suggested.

Thanks for the quick response

@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Development

No branches or pull requests

3 participants