OnLink
When a scan flags a repo, someone has to work out who owns it, whether it is really public and whether anyone still works on it. OnLink now imports GitLab projects and groups into Jira Service Management Assets, so those answers are on the ticket.
Repository facts live in GitLab, but the questions about them arrive in Jira: security findings, access requests and incidents. Without a link between the two, every ticket starts with a search.
Every project references its GitLab group, so findings and requests route to the team that owns the code.
Visibility is an attribute. One Assets search lists every public repository.
Last activity, archived and empty-repository flags turn repo sprawl into a saved filter.
GitLab sits next to AWS, Google Cloud, Azure, devices and people from OnLink’s other 100+ sources.
The requester picks the repository from an Assets field. The agent sees the owner group, visibility, last activity and archived state next to the request, without opening GitLab.

▶ 60-second short
No time to read? The Short covers the whole flow, from the scanner alert to saved searches.
One API call becomes two Assets object types, GitLab Projects and GitLab Groups, linked by a reference so every repository carries its owner.
Setup comes down to three parts. The setup guide has every step, sample responses and the full mapping table.
Create a GitLab group access token with the Reporter role and the read_api scope, then add it to OnLink as a Bearer token.
OnLink calls GET /api/v4/projects?membership=true, or the group projects endpoint, 100 projects per page. Filters such as active=true or visibility=private limit what you import.
Key projects on the numeric project ID so renames never create duplicates, map the fields you need, link each project to its group and schedule the import.
Sample mapping for GitLab projects:
key:id=ProjectID
map:name=Name
map:path_with_namespace=Full Path
map:web_url=URL
map:visibility=Visibility
map:archived=Archived
map:empty_repo=Empty Repository
map:last_activity_at=Last Activity
map:namespace.id=Group|GroupID=${namespace.id}
map:topics=Topics|Name=${topics}
OnLink is one app with 100+ connectors. GitLab joins AWS, Google Cloud and Azure, plus HR systems, identity providers, device managers and security tools, all feeding the same Assets schema.
Each repository is an Assets object, so the questions people ask in Slack become saved AQL searches:
| Question | AQL |
|---|---|
| Which repos are public? | objectType = "GitLab Project" AND Visibility = "public" |
| What has gone stale? | objectType = "GitLab Project" AND "Last Activity" < now(-90d) AND Archived = false |
| Who owns it? | objectType = "GitLab Project" AND Group = "payments" |
| Which repos are empty? | objectType = "GitLab Project" AND "Empty Repository" = true |
| Which production repos are public? | objectType = "GitLab Project" AND Topics = "production" AND Visibility = "public" |
Start a free trial of OnLink on the Atlassian Marketplace and connect GitLab with a read-only token.
Yes. OnLink imports GitLab projects and groups from the GitLab REST API into Assets object types, with a reference from each project to its group.
Yes. Use your own host as the base URL, for example https://gitlab.example.com/api/v4. GitLab Dedicated works the same way.
A group or personal access token with the read_api scope. A Reporter-role group token is enough, and it cannot push code or change settings.
On GitLab.com, the projects endpoint without membership=true returns every public project. Add the filter or use the group projects endpoint.
You set a schedule per import: hourly, daily, weekly or monthly. GitLab updates last activity at most once an hour, so hourly is the most you need.
GitLab in Assets
Start a free trial of OnLink on the Atlassian Marketplace and bring GitLab projects and groups into Assets.
Your service desk shouldn’t have to ask who owns a repository. Bring GitLab projects and groups into Assets and put the owner on every ticket.
What you get with OnLink for GitLab:
RELATED