What this article covers:
- What is synced between Jira projects
- What is not synced
- Jira-Jira customization options
You can use Unito to share Jira issues from one project to another and keep their comments, due dates, assignee, attachments, and custom fields synced. Keep team members in their own Jira projects and import or export only a selected portion of Jira issues with Unito's powerful rules.
What is synced?
See a field you'd like to sync that’s not listed? Contact us! We may already support it through a manual configuration.
What is not synced?
- Jira Sprints: Currently, these are read-only; supporting two-way syncing is on our roadmap.
- Jira links and dependencies: On the roadmap.
- Jira time tracking: On the roadmap.
- Mentions: Unito does not support user mentions in titles, descriptions, or comments just yet.
Is there a feature you would really like? Contact us! We prioritize based on user requests.
Here are all the available options for Jira:
Filter issues by labels
Unito will sync all 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 one Jira project to the other. Here is how it works.
Map your Jira users
Sync closed work items
Unito will automatically sync open items automatically. But here is how you can sync closed items.
Prefix item title with Jira issue number
Unito doesn't sync the issue number by default but you can enable that (for either Jira project) in your flow 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 Jira.