Guide
GitLab integration allows importing Projects, Branches, Labels, Issues (with Milestones), and Merge Requests into Fibery. Don't worry, you can skip archived projects if needed. It is also possible to sync Reviewers & other user-oriented fields.
The most interesting use case is to import Merge Requests and attach them to real work items, like Features, User Stories, or Tasks so Merge Requests statuses are visible right in Fibery.
🚨 Note that only main(master) branches can be synced. If this is not enough for you, please let us know in the Intercom
🚨 Every User has to be a part of the Git organization in order to be properly synced. At the moment, there is no way to sync Users who are not a part of the member list, even if they were previously a part of the project.
Setup GitLab sync
Note: to set up this integration, you have to have enough access to your GitLab sources. Ex., Group is included in the list only if your account has at least "GUEST" access.
Navigate to Templates and find GitLab template
Click Sync.
Authorize the GitLab app.
Choose what databases you want to sync from GitLab.
Specify starting date for the sync. The default is set to sync the last 30 days, but go ahead and fetch all the data if you need it.
Click Sync now and wait for the magic to happen. Once the GitLab Space appears in the sidebar, all the data should be synced.
You can also synchronize Subgroup members in this integration.
Link Merge Requests to Features (or any other Database)
To have these connections, you have to encode Feature Id in your Merge Requests. In our team, we include Feature Id into a Merge Requests name, like this:
[feature/2013] Documents ant Whiteboards collections on entity as extensions
The main idea is to extract Feature Id from Merge Request name and link Feature and Merge Request Databases via automatic rule (How to link entities automatically between databases). This is a two-step process.
Step 1. Create Feature Id formula field inside Merge Request
Open any Merge Request and add a new formula. In Fibery's case, the formula looks like this:
Here is the formula for your convenience:
If(StartsWith(Name,"\[feature/"),Trim(ReplaceRegex(Name,"\[feature\/(\d+).+"," \1 ")),"")
Step 2. Create an automatic connection between Merge Request and Feature
Inside a Merge Request, create a new Relation field. Set relation to Feature, and set automatic rule to match any Merge Request with a Feature by Id:
As a result, you will have the following info:
Inside a Feature you will see a list of Merge Requests:
FAQ
I have error: Unable to fetch commits pipelines for <accountname>:403 forbidden
This is a GitLab http error: [GET 403] https://gitlab.com/api/v4/projects/33016488/pipelines?sha=db30a2c5d59b0ade745514f6a4adb7ba30f739d8&sort=desc&order_by=updated_at&per_page=1 403 Forbidden
Most likely user, that is responsible for Fibery integration doesn't have enough access to Gitlab.
If that's not the case - please, contact us in the chat. 🙏
GitLab users who are flagged as "guests" in GitLab aren't being synced to the "Members" database in Fibery
Inheritance works in another direction in GitLab API (for members).
Let's say
Parent group - User A; User B
Child group - User A; User C;
If you select parent group then you will receive: A, B
If you select child group then you will receive: A B, C
Do you have a VPN solution for on-premise GitLab setup?
We do not provide a VPN solution for on-premise GitLab setups. However, one potential workaround would be to allow Fibery IP addresses ranges ad open them for communication so that the integration can function properly. This can be done by configuring a firewall rule that allows specific traffic to and from the Fibery IP addresses.
These addresses are:
18.198.169.41
18.196.77.165
3.124.79.168
Please contact us if you need more detailed information about Fibery IP addresses.
Can I fetch data from multiple Gitlab project groups?
Currently, the case with multiple project groups is not one we can support in a nice way.
If you need multiple sources at the same time - as a workaround we can suggest schema 1 integration = 1 organization/project
Why does my account keep expiring?
If your GitLab integration in Fibery keeps disconnecting or asking to reconnect, here’s what’s happening and how to fix it.
GitLab automatically invalidates all refresh tokens linked to the same GitLab account whenever one of them is refreshed.
This behavior is not compliant with the OAuth specification, but it’s how GitLab currently works.
As a result, if you have:
Multiple integration accounts in the same Fibery workspace linked to one GitLab account, or
Several Fibery workspaces all connected to the same GitLab account
then refreshing one connection will cause all others to expire.
Example:
→ When Fibery A refreshes its GitLab token, Fibery B’s token becomes invalid. Next time B tries to sync, it fails and asks you to reconnect.
To avoid this issue:
Use only one GitLab integration account per GitLab user.
If you need to connect multiple Fibery workspaces, create a separate GitLab user for each workspace (for example, fibery-sync-1@example.com, fibery-sync-2@example.com).
Right now:
If your connection expires, you’ll need to remove the integration and reconnect it manually.
User emails are not synced
That's a tricky limitation for the Gitlab side.
You can only sync emails, that are marked as public.
And making email public in Gitlab is a User's preference at the moment. So every Gitlab user has to change that setting, so Fibery could sync it.
Here is a Gitlab's community post on that with more details.
I want to link several entities to another entity
You can link multiple entities to another entity in Fibery using automations or scripts — for example, to connect several Tasks to a single Project.
The simplest approach is to use the addCollectionItem command or a GraphQL mutation that updates the relation field. With GraphQL, you can first query the entity IDs you want to link, and then add them all at once to the related collection.
Example workflow:
Find the entities you want to link (e.g., all Tasks with a specific tag).
Retrieve their IDs via fibery.graphql().
Use addCollectionItem (or a similar mutation) to attach them to the target entity.
This pattern works for any “many-to-one” or “many-to-many” relationships in Fibery — such as linking multiple Bugs to a Release, multiple Articles to a Topic, or multiple People to a Company.
This community discussion is a nice way to learn about options.