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

Dashboard: Organization repositories no longer show up on dashboard (even when the user belongs to them) #6195

Closed
2 of 7 tasks
bkraul opened this issue Feb 26, 2019 · 10 comments · Fixed by #6897
Closed
2 of 7 tasks
Labels

Comments

@bkraul
Copy link

bkraul commented Feb 26, 2019

Description

It used to, that all repositories for the organization you belonged to would show up on the repositories list on the dashboard page. This is no longer the case, and only your own repositories and other users' forks to which you were given express access show up. I am the owner of one of the organizations, and there are upwards of 50 repos in the organization, and I can see none of them. I cannot even search for repositories using Explore/Repositories. I have to end up browsing the organization and then searching in there.

Has behavior changed by design? Is there a property I need to turn on in order to see all the repositories of the organization I own on my dashboard? My user is not an admin user, but it is a user flagged as the organization's owner.

@lunny
Copy link
Member

lunny commented Feb 27, 2019

Could you search them on the dashboard?

@bkraul
Copy link
Author

bkraul commented Feb 27, 2019

No, that's the point. I used to. Now I cannot. The only way I can search them is by going to Explore -> Pick the organization, and search within the organization.

@bkraul
Copy link
Author

bkraul commented Mar 8, 2019

Any news on this?

@lunny
Copy link
Member

lunny commented Mar 16, 2019

Cannot reproduce this and could you reproduce this on https://try.gitea.io or https://gitea.com?

@bkraul
Copy link
Author

bkraul commented Mar 17, 2019

I am not sure if I will be able to replicate there, as this behavior involves a user that once was system admin, and then it was demoted to user but still is an organizational owner, but I will see what I have to work with and get back with you.

@bkraul
Copy link
Author

bkraul commented Mar 21, 2019

I was able to reproduce it on https://try.gitea.io . The source of the issue seems to be the Private flag for the organization. When the organization is set to Public which is the default on creating an organization, all the repositories show for all the members:

image

But If you flag the organization as Private (Visible only to organization members), the dashboard no longer shows any organizational projects, only your own projects, forks or collaborative projects. This happens no matter if you switch the dashboard context to the specific organization.

image

image

I mean, you can see all the events in the feed, but all of the sudden, the organizational projects are no longer there. And these are not just organization members, they are Owners of the organization. I hope this helps.

@bkraul
Copy link
Author

bkraul commented Mar 21, 2019

I can also verify that the projects do show up if the organization is set to Limited (Visible to logged in users only), but, the idea is that we do not even want information about the organization or its projects seen by logged in users that are not part of the organization. But members, definitely should be able to see all organizational projects in dashboard.

@zeripath
Copy link
Contributor

The problem is that the API route /api/v1/repos/search is incorrect and needs to be changed.

@lunny lunny added the type/bug label Mar 22, 2019
@bkraul
Copy link
Author

bkraul commented Apr 16, 2019

@lunny Is there currently a milestone or a target version release for this?

@lunny
Copy link
Member

lunny commented Apr 19, 2019

@bkraul Nobody are working on this. but I think this should be fixed on v1.8.0 or v1.8.1

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.

3 participants