GitLab
OAuth tracker where labels are the board: status changes swap labels, closing an issue retires its task.
GitLab connects over OAuth: Connect GitLab — to gitlab.com, or to your own instance when the host is configured for it. One connection per organization.
- Import unit: a GitLab project. Open issues import; closed ones don't.
- Labels are the columns. GitLab issues are natively just open/closed, so the community convention applies: your status labels form the board, plus a synthetic Open column for unlabeled issues. Peractor's outbound status change removes the old status label and adds the new one — other labels untouched; moving to Open just clears the status label.
- Closing an issue retires its task. Since only open issues import, the panel shows work in progress, never an archive. This is GitLab-specific and worth knowing before you wonder where a task went.
- Sync is by poll (~30 seconds). Published artifacts upload inline into issue notes.
The OAuth tracker covers issues. Merge requests — runs pushing branches and opening MRs — use a git credential from Settings → Git access, which works for gitlab.com and self-managed instances alike.