You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
[x]
):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
The text was updated successfully, but these errors were encountered: