This use case describes how you can synchronize one Jira project with multiple other projects. This can be helpful when you:
- Manage all tasks in one Jira project, while not all tasks are done by your team, but also by teams or companies which don't work in your Jira project.
- Work for multiple teams or companies but want to collect all tasks in one Jira project.
To do this, set up multiple synchronizations, one for each project you want to connect to the single project. Backbone takes care of the automated issue synchronization. You can choose if you want to share certain tasks with multiple partners, or only each task with a specific partner.
In this guide, we will configure a Jira project (project A) so it synchronizes issues with multiple other projects (project B and C).
- Create a new synchronization between project A and B
- Configure issue type and field mappings according to your needs.
- Setup a JQL query to limit the issues you want to sync with project B. We recommend you to use Jira's advanced search to find criteria which suits your needs, e.g. "component = projectB".
- Create another synchronization between project A and C. We recommend you to use a different synchronization user (see also "Good to know" section).
- Configure issue type mappings and field mappings according to your needs.
- Setup a JQL query to limit the issues you want to sync with project C. We recommend you to use Jira's advanced search to find criteria which suits your needs, e.g. "component = projectC".
Good to know
- If you want to synchronize the changes not only from project B to A, but also from B to C via A, you will need a different synchronization user for the connection details of project A. We recommend you to use different synchronization users so you can decide later if you want that behavior. Please note that in Cloud to Cloud scenarios, you cannot use different synchronization users at the moment.
- If you want to synchronize each task with one partner only, make sure your JQL queries are well-defined and tasks don't accidentally qualify for multiple synchronizations. A single select field can be a perfect criterion.