Our GitLab integration allows you to import merge requests and issues to better track development activities across all - or selected - projects in one place. 

Development items are automatically prioritized based on due dates and recommended actions. Issues and merge requests can also be cross-referenced (auto-linking) and aggregated to further optimize your priority inbox.

Note on security we do NOT fetch your code. Keypup doesn't need to access your code in order to evaluate priorities on development items. Be assured that if we ever needed to access your code in the future in order to deliver a new feature we would make it an opt-in feature. See section below "What data do we collect?".

Also important: we NEVER update data automatically in third-party applications. Updates in third-party applications are ONLY performed under your control via remote actions. See section below "What remote actions can you perform?".

> What data do we collect?

Our GitLab integration fetches the following entities:

  • Comments: used for display in the dashboard

  • Commits: used to detect links between issues and pull requests

  • Issues: used for display and auto-linking to merge requests. Due dates on issues are factored when evaluating the due date of related merge requests.

  • Labels: used for display in the dashboard. Labels on issues are also applied on related merge requests.

  • Milestones: used to retrieve the due date of items.

  • Merge requests: used for display on the dashboard. Merge requests can reference issues via auto-linking (title or description) and nest them in the Priority Inbox.

  • Merge request approvals: used to evaluate the review/approval status of merge requests and recommended actions.

  • Merge request build statuses: used to evaluate the readiness of a merge request and recommended actions.

  • Suggested reviewers: used to detect who are the reviewers of a given merge request. If reviewers are on Keypup then the item will appear in their Priority Inbox.

> What remote actions can you perform?

Our GitLab integration allows you to perform the following remote actions from the dashboard:

  • Link merge requests and issues: merge requests and issues can be linked to each other directly from the Priority inbox using the link icon. In order to link items we update the description of the parent merge request and add a closes: https://issue-url.domain auto-linking keyword at the bottom of it.

  • Merge pull requests: approved merge requests with a green build - if any - and a mergeable status can be merged directly from the Priority Inbox and Review & Merge board.

  • Quick reply on items: it is possible to comment on a merge request or an issue from the Priority inbox. For issues replies can be done either directly on the issue or via the issue activity feed when an issue is nested under a merge request.

> How often do we refresh data?

Updates from GitLab are received in real-time via webhooks except for Labels and Milestones, which have to be long polled on GitLab every 20 minutes.

If for any reason we are unable to setup real-time updates on GitLab - e.g. the user who connected GitLab has no admin access on a given project - then we revert to long polling data every 20 minutes.

Whenever possible we recommend connecting GitLab projects as an admin to get the best experience.

Simply use the URL or #id ('#' + 'id') or reference (org/project#123) of a GitLab issue in your merge request title, description, or in one of your commit messages.

Example of GitLab issue

E.g. linking via merge request title

  • The issue is in the same project as the MR: #9 My MR title 

  • The issue is in a different project: QA1Corp/project1#6 My MR title 

E.g. linking via merge request description

This is my MR description.

# Via URL
closes: https://gitlab.com/QA1Corp/project1/-/issues/6

# Via ID if the issue is in the same project as the MR
closes: #6

# Via reference if the issue is in a different project
closes: QA1Corp/project1#6

E.g. linking via commit message

# Via reference if the issue is in a different project
QA1Corp/project1#6 My commit title

- Decrease popover delay

# Via reference using auto-linking keywords
closes: QA1Corp/project1/#6

# Via URL
closes: https://gitlab.com/QA1Corp/project1/-/issues/6

# Via ID if the issue is in the same project
closes: #6


Did this answer your question?