Skip to content

Team members able to see issues for private repositories not part of team #4029

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

Closed
2 of 7 tasks
bkraul opened this issue May 23, 2018 · 1 comment
Closed
2 of 7 tasks
Labels
Milestone

Comments

@bkraul
Copy link

bkraul commented May 23, 2018

  • Gitea version (or commit ref): b574af2
  • Git version: 2.15.0
  • Operating system: Ubuntu 18.04 LTS (docker)
  • 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

This issue was discovered trying to target the opposite situation. Basically what happens is that when a team is added to an organization, the user in the team can see the list of issues for all projects in the organization, but not able to click on them (getting instead a 404 error).

The correct behavior should be that no issues for private repositories should be visible if the repositories are not part of the team in question.

Screnshots

image
image

@techknowlogick
Copy link
Member

Closed with #4034

@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

No branches or pull requests

3 participants