Tuskway for GitLab
GitLab issues from a plan your team signed off.
Teams on GitLab, including self-managed GitLab, can run the same workflow as everyone else: agree on the design in Tuskway, split it into tickets, and publish them as GitLab issues. From there, edits on either side are tracked.
What changes
What GitLab gets from Tuskway.
gitlab.com or your own server
Connect with GitLab sign-in, or paste an access token and the address of your self-managed instance. Secrets are encrypted before they are stored.
Two-way sync
Status and assignee move both ways. Tuskway adds its own labels and reads back the ones your team sets. An edit made on the GitLab issue is flagged in Tuskway for an editor to accept or dismiss.
A brief behind every issue
The issue is created from a ticket brief with a goal, acceptance checks and the files to touch, tied to the design section that explains it.
How it works
From a reviewed plan to GitLab.
- 01
A workspace owner connects GitLab from the Trackers page, with sign-in or an access token.
- 02
On an epic, pick the GitLab project to publish to.
- 03
Publish. Each ticket brief becomes a GitLab issue.
- 04
Keep working in either place. Differences show up in the epic's inbox for a decision.
FAQ
GitLab questions.
Does it work with self-managed GitLab?
Yes. The owner gives the address of the server when connecting. Your server has to be reachable from Tuskway.
What does Tuskway store from GitLab?
The connection, the project you publish to, and for each published issue its link, title, description, status, assignee, labels, and who last changed it and when, so it can show when the issue and the ticket differ.
Does Tuskway need access to our repositories' code?
No. It lists projects, creates and updates issues, and receives issue changes.
On another tracker? Same plan.
Publish to GitLab from a plan your team agreed on.
Connecting a tracker is optional. Tuskway never needs access to the code.