GitLab
Link merge requests and issues to tasks, see their live status, and complete tasks when they merge or close.
GitLab connects through a webhook, so it works with gitlab.com and self-managed GitLab. Add one connection per GitLab project, or one for a whole group.
Connect a project or group (admins)
- 1In JinkoUp, open Settings and find the GitLab card. Click Connect GitLab (or Add project or group).
- 2Keep https://gitlab.com, or enter your self-managed GitLab's address, and click Create webhook.
- 3In GitLab, open the project or group and go to Settings → Webhooks → Add new webhook.
- 4Paste the URL and Secret token from JinkoUp (use the copy buttons).
- 5Under Trigger, tick Merge request events and Issues events, then click Add webhook.
The connection shows Last event once GitLab sends something. Use GitLab's Test → Merge request events to check it straight away.
Connect a group to cover every project in it at once (group webhooks need GitLab Premium). On the Free tier, add the webhook to each project.
Link a merge request or issue to a task
- 1Open the task and click Copy for PR (or Copy for MR) next to Pull & merge requests. This copies
Closes <task link>. - 2Paste it into the merge request's or issue's title or description in GitLab.
It appears on the task with a live status (Open, Draft, Merged or Closed). Any JinkoUp task link works, even without “Closes”.
Complete tasks automatically
Put closes, fixes or resolves right before the task link. The task completes when the merge request merges, or when the issue closes.
Closes https://jinkoup.com/projects/…?task=…Comment back on GitLab (optional)
Add an access token to the connection and JinkoUp comments “🔗 Linked to JinkoUp” on merge requests and issues when they're linked.
- 1In GitLab, open the project or group, then Settings → Access tokens → Add new token.
- 2Give it the Reporter role and the api scope, and create it.
- 3In JinkoUp, open the connection on the GitLab card, paste the token under Comment back on GitLab and click Save.
- Removing the link from the description unlinks it.
- Titles of tasks in private projects aren't shown on GitLab.
- Only tasks in the workspace that created the connection can be linked.
- To stop, an admin clicks Delete connection, and should also remove the webhook in GitLab.
Keep the secret token private: anyone with the URL and token could send fake events. If it leaks, delete the connection and create a new one.
Related articles
Still stuck? Tell us what you were trying to do and we'll help.
Contact support