Here's a breakdown of what Unito's GitHub integration can't do yet — and a few other considerations.
Unito's GitHub integration is designed to get crucial data out of your repositories and into other tools. You've seen what Unito can do for GitHub users, so this article will cover what it can't do — yet.
What this article covers:
Unsupported fields
While Unito's integration for GitHub supports most of the tool's fields, there are some it doesn't support.
- Subtasks: Since GitHub only supports parent tasks, Unito can't sync subtasks or checklists from other tools to GitHub. There is a workaround for this, however.
Unsupported mappings
- GitHub labels with some fields: Because GitHub's label field is a multi-value dropdown, it can only be mapped to other multi-value dropdown fields — such as other label fields.
- Comments and descriptions can't sync to text-based fields in tools such as Google Sheets or Microsoft Excel. You can only sync comments with other tools that have comment functionality.
- Pull requests with subtasks
Other limitations
- GitHub projects: Unito doesn't support GitHub projects. Issues connected to both a repo and a project will continue to sync, but you can't select a GitHub project as a block of work.
- Permissions: Unito needs certain read & write permissions in order to work. You can get a full breakdown of these permissions here.
- On-premise: In order for on-premise GitHub accounts to connect to Unito, it needs to be accessible via the internet. If that isn't the case, please read our guide to set this up, or contact us if you’re not sure how to proceed!