Namespace bugs
Created by: pdf
As of df03275e:
- Namespace selected in dropdown during project creation is ignored, new projects are always created in user's namespace
- Namespace selection via Admin -> Projects -> Edit dropdown does not invoke Gitlab::ProjectMover, resulting in broken projects (namespace updated in DB, but repository not moved on disk).
- Namespaces not displayed in
Add User to Projectsautocomplete list (though perhaps this is overlooked due to upcoming group permissions? ;-) )
Activity
Created by: rtripault
Jumping in since i did the upgrade last night (with Gitolite 2)
- some previous users no more had the right to pull/push, i had to switch their roles
- projects count in the groups is broken (from dashboard only, count is fine when browsing gitlab/groups/groupname)
- editing an "old" project (not yet namespaced) pre-fills the namespace dropdown with the owner namespace instead of "global"
By Administrator on 2012-11-30T22:07:38 (imported from GitLab project)
By Administrator on 2012-11-30T22:07:38 (imported from GitLab)
Created by: riyad
+1 on @rtripault's issues I also had
- all branches and tags gone from repo after move
By Administrator on 2012-11-29T12:52:13 (imported from GitLab project)
By Administrator on 2012-11-29T12:52:13 (imported from GitLab)
Created by: rtripault
@Riyad i would bet that's because your repository is not in the "namespace folder". Check if you find it in
/home/git/repositories/{namespace}/{repository.git}, if notsudo mv /home/git/repositories/{repository.git} /home/git/repositories/{namespace}/{repository.git}By Administrator on 2012-11-29T13:17:15 (imported from GitLab project)
By Administrator on 2012-11-29T13:17:15 (imported from GitLab)
Created by: chopmann
As of : cf8b3692 -Under Admin Area: If you Edit a Project the Namespace defaults to Administrator, even if the Project is under another namespace
By Administrator on 2012-11-29T13:22:15 (imported from GitLab project)
By Administrator on 2012-11-29T13:22:15 (imported from GitLab)
Created by: dzaporozhets
This one should fix most of bugs eb1004f7
By Administrator on 2012-11-29T14:29:14 (imported from GitLab project)
By Administrator on 2012-11-29T14:29:14 (imported from GitLab)
Created by: pdf
As of 0530e5ba:
Namespace selected in dropdown during project creation is ignored, new projects are always created in user's namespaceNamespace selection via Admin -> Projects -> Edit dropdown does not invoke Gitlab::ProjectMover, resulting in broken projects (namespace updated in DB, but repository not moved on disk).- Namespaces not displayed in
Add User to Projectsautocomplete list (though perhaps this is overlooked due to upcoming group permissions? ;-) ) projects count in the groups is broken (from dashboard only, count is fine when browsing gitlab/groups/groupname)editing an "old" project (not yet namespaced) pre-fills the namespace dropdown with the owner namespace instead of "global"
Looks like just about all of the issues mentioned so far are resolved...
By Administrator on 2012-12-03T02:12:04 (imported from GitLab project)
By Administrator on 2012-12-03T02:12:04 (imported from GitLab)
Created by: dzaporozhets
Fixed
Namespaces not displayed in Add User to Projects autocomplete listby d8398921By Administrator on 2012-12-04T13:26:40 (imported from GitLab project)
By Administrator on 2012-12-04T13:26:40 (imported from GitLab)
Created by: riyad
Scenario: I have 2 users as masters in a project And the project is in one of the user's namespace (e.g. "user_a/project_foo") When I try to edit the project as the other user (e.g. "user_b") Then I the current namespace should be selected (i.e. "user_a")
Currently there isn't even "user_a" in the namespace selection (when I edit the project as "user_b") and my user namespece (i.e. "user_b") is preselected! So whenever I change something else on the project, I automatically change the projects namespace.
By Administrator on 2012-12-04T19:28:57 (imported from GitLab project)
By Administrator on 2012-12-04T19:28:57 (imported from GitLab)
Created by: riyad
Scenario: When I change the project namespace Then the team should get a notification (mail) And it should tell me about the change And it should contain the new project url (maybe also RSS) And it should tell me how to change the remote on my repo (i.e.
git remote set-url origin ...)By Administrator on 2012-12-04T19:34:16 (imported from GitLab project)
By Administrator on 2012-12-04T19:34:16 (imported from GitLab)
Created by: dzaporozhets
Dont allow masters to change project namespace 2a1c5cdf
By Administrator on 2012-12-04T20:08:12 (imported from GitLab project)
By Administrator on 2012-12-04T20:08:12 (imported from GitLab)
Created by: riyad
What would happen if I'm Admin, but not the owner or a member of the project? Can I still change the namespace?
@randx You also need to update the permissions help page.
By Administrator on 2012-12-04T20:19:48 (imported from GitLab project)
By Administrator on 2012-12-04T20:19:48 (imported from GitLab)
Created by: dzaporozhets
Admin can change project napespace to any from admin area e376f315
By Administrator on 2012-12-04T20:55:01 (imported from GitLab project)
By Administrator on 2012-12-04T20:55:01 (imported from GitLab)
Created by: riyad
@randx We still need a solution for the scanario in https://github.com/gitlabhq/gitlabhq/issues/2113#issuecomment-11011742
By Administrator on 2012-12-06T17:19:27 (imported from GitLab project)
By Administrator on 2012-12-06T17:19:27 (imported from GitLab)
Created by: riyad
Closing this, because all but the notification issue were fixed. Opened #2294 (closed) for notifications.
By Administrator on 2012-12-17T17:21:52 (imported from GitLab project)
By Administrator on 2012-12-17T17:21:52 (imported from GitLab)
