"403 Forbidden" syncing milestones with Gitlab integration

Bugs & Issues
1

Hi,

It is great that the Gitlab integration is now also offering milestone sync. However, it gives me a “403 Forbidden” error.

When I trigger the Gitlab sync, it starts normally: syncing projects, merge requests and issues.

Then the “403 Forbidden” error occurs. The milestone database remains empty afterwards.

I tested:

  • reauthenticating → the error persists
  • deselecting milestones from the sync via the sync configuration → everything works as expected. But enabling milestones again brings back the 403.

Sorry that I cannot share screenshots since “new users can only put one embedded media item in a post.“ But I hope it is descriptive enough.

1 Like
2

Hi,

What kind of access do you have to your projects (maintainer, viewer, etc)? E.g. project 66031889 (if I found properly)

You can inspect your permissions via direct API call https://gitlab.com/api/v4/projects/{project_id} . Find permissions sections in response and share it please.

A valid access level Possible values: 
0 (No access), 
5 (Minimal access), 
10 (Guest), 
15 (Planner), 
20 (Reporter), 
30 (Developer), 
40 (Maintainer), 
50 (Owner).

According to gitlab spec Reporter access level is required.

3

I am Developer (30) for this specific and most other projects. I can see / access milestones also via the browser.
This particular project does not have milestones. Instead Group Milestones were used to manage issues within this project.
We have both, some project milestones and most are group milestones.
Could group milestones be the issue?

Issues can be linked to group or project milestones. In the issues API, you only recognize the difference because the corresponding milestone has either a project_id or a group_id.


{
  "id": ...,
  "project_id": ...,
  "milestone": {
    "id": ...,
    "project_id": ...,
  },
}

vs

{
  "id": ...,
  "project_id": ...,
  "milestone": {
    "id": ...,
    "group_id": ...,
  },
}
4

Made some changes. Could u try again, please?

5

Thanks for the quick upate!

The sync now finishes without errors.
Milestones - both project and group milestones - are synced and issues are linked to the corresponding milestones.

I could only find one issue:
The Gitlab Link in the Milestone is incorrectly formatted for Group Milestones.

Project milestones have the URL “https://gitlab.com/[path to group/project]/-/milestones/[id]“ (as correctly specified in Fibery)
However, Group milestones have a prefix ‘groups’ prefix added to the path:
“https://gitlab.com/groups/[path to group/project]/-/milestones/[id]”

6

Thank you for pointing out this issue. I’ve fixed it. The updated URLs will appear after the next sync.

7

Nice. It works. Thanks!

1 Like