What this article covers:
- What is synced between Jira and GitHub
- What is not synced
- Jira-GitHub sync customization options
Bitbucket isn’t the only Git solution that plays nicely with Jira anymore. With Unito, you can seamlessly use Jira for your issue tracking and GitHub for version control. Here's how these two tools come together with Unito.
What is synced?
Have a field you want to sync that’s not listed? Contact us! We may already support it through a manual configuration.
What is not synced?
Is there a feature you'd like to see implemented? Let us know!
Here are all the available options for Jira and GitHub:
Filter issues synced
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 to Jira (complete guide)
You can choose to sync only from GitHub to Jira or Jira to GitHub. Here is how it works.
Map your Jira and GitHub 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.
Prefix task title with Jira/GitHub issue number
Unito doesn't sync the issue number by default but you can enable that (for either Jira or GitHub) in your sync settings. Here is how to do it.
Default type for new Jira issues
You can choose which type of issue should be created by default in Jira when a new issue is created in GitHub.