What this article covers:
- What is synced between GitLab projects
- What is not synced
- GitLab-GitLab sync customization options
Collaboration between two private or public repos has never been easier! Now, with Single Tool Sync, you can work with another organization's repos without having to request access to their entire GitLab organization. Check out the guide below for what we sync, and how we sync it.
What is synced?
See a field you'd like to sync that is not listed? Contact us - we may already support it through a manual configuration.
What is not synced?
Do you have a feature you'd really like? Contact us! we prioritize based on user requests.
Here are all the available options for GitLab:
Filter by label
Unito will sync all tasks and issues by default but you can customize your workflow by syncing just some of them (complete guide).
Filter by issue type
You can filter which type of issues you want to be synced between projects (Issue, Pull-Request, or both) (complete guide).
You can choose to sync only from one GitLab project to another. Here is how it works.
Map your GitLab users
Sync tasks/issues already closed
Unito will automatically sync opened tasks or issues automatically. But here is how to also sync closed tasks and issues prior to the sync creation.
Add GitLab issue number to task title
Unito doesn't sync the issue number to the opposite GitLab project by default but you can enable that in your sync settings under the relevant GitLab tab. Here is how to do it.