Accessing the list of milestones for a group of projects is no longer possible, even though individual milestones are still accessible (e.g. https://gitlab.com/groups/sis-cc/.stat-suite/-/milestones/27), and it is still possible to create new milestones using the GitLab API v.4.
@j3an-baptiste Hi, thanks for raising it. I noticed that you have a sub-group named .stat-suite which starts with a dot '.'. Dots are not allowed in group/project paths. Could you please confirm that renaming the sub-group to something without a dot helps you to resolve this issue?
@kategrechishkina Hello! And thanks for your reply!
Our sub-group named .stat-suite with a dot was created this way a long time ago, and it didn't make any issue before. I didn't make the test of removing it, because it would have many unexpected impacts in our entire environment and paths.
After checking the GitLab documentation here, I can see that, unless the doc is not up-to-date, dots in path are allowed...?
Hi. My group name contains only lowercase letters and one digit in the middle of the name and I can see the same issue. Already reported and waiting for a solution.
@j3an-baptiste You are right. The documentation needs updating. I have created an MR !54848 (merged) to do that to align with our current requirements.
I tried creating a test group that started with a dot:
The name of the group cannot start with the dot.
The Group URL can start with the dot.
It is possible that you would only need to rename The group name and leave the namespace as it is now. Which might have fewer consequences for your organization.
@kategrechishkina thanks, I've made the test in renaming the group without dot, unfortunately the issue is still there. I suspect an issue somewhere else, because the list of milestones from the group on top of the sub-group with a dot also returns a 500 error : https://gitlab.com/groups/sis-cc/-/milestones
No route matches {:action=>"index", :controller=>"projects/releases", :group_id=>"sis-cc", :namespace_id=>nil, :project_id=>nil}, possible unmatched constraints: [:namespace_id, :project_id] from /opt/gitlab/embedded/service/gitlab-rails/config/routes.rb:310:in `block (3 levels) in <top (required)>' from action_dispatch/routing/route_set.rb:155:in `block (2 levels) in add_url_helper' from /opt/gitlab/embedded/service/gitlab-rails/app/views/shared/milestones/_milestone.html.haml:28:in `_app_views_shared_milestones__milestone_html_haml___4582057402455614744_3204360' from /opt/gitlab/embedded/service/gitlab-rails/app/views/groups/milestones/_milestone.html.haml:1:in `_app_views_groups_milestones__milestone_html_haml__3804280631606875153_3204340' from action_view/helpers/rendering_helper.rb:38:in `render' from /opt/gitlab/embedded/service/gitlab-rails/app/views/groups/milestones/index.html.haml:22:in `block in _app_views_groups_milestones_index_html_haml__3215789208063427025_3204220' from /opt/gitlab/embedded/service/gitlab-rails/app/views/groups/milestones/index.html.haml:18:in `_app_views_groups_milestones_index_html_haml__3215789208063427025_3204220'
This seems to be broken since the introduction of group milestones association with releases in 13.6, marking as severity2 since there's no real workaround, other than removing the releases from linking to the group milestone. Since we don't have a "releases" page for groups either, to show the full paginated list of releases, it may not be an easy fix (unless we remove the linking to "more releases" for the group view in the meantime)
Just got word from the customer that the workaround we provided in the ticket partially worked (remove the link between project releases and group milestones for the specific groups where they see this).
The customer's feedback was also that they'd like this fixed as soon as possible (and if possible to increase the severity).
Assuming we are moving forward with just removing the link on group milestone pages (see discussion above), I think this would be doable in 1 MR (weight of 1).
It should be as simple as conditionally removing the link group pages and adding a test to cover this case.