Linking Jira instances via J2J Issue Sync
14. September, 2018
The popularity of Atlassian tools is steeply growing and the products of this Australian company are adopted by more and more new customers every year. In the first place, it is the Jira, an issue tracking software, the popularity of which is growing. To manage their projects, it is used by companies that operate as a supplier as well as a client. Frequently, there might be problems with communication and information sharing between these two partiers. Fortunately, there is an easy solution
Everybody has their own Jira instance
We know, how complicated it is to organise a good collaboration with a customer from the perspective of a supplier who is at the same time also a user of the Atlassian Jira tool. It is especially very complex in case of the projects that require a frequent communication between two parties. For instance, we are talking about a transition phase of the project, especially about UAT (acceptance testing) or about the handover of outputs of each agile sprint to be tested at the customer’s place.
On the one hand, it is us as a supplier who uses Jira to organise own deliveries. On the other hand, there is our client who uses their own Jira instance to report and record bugs. Moreover, for the client, our delivery is often just one among many others within a framework of a complex project.
The difference between the needs of the client and the supplier is crucial
As a supplier, we need to have, at each stage of the delivery, as fresh as possible inputs for our implementation team. We want to have all information in one place and not to scatter the attention of the team unnecessarily. Simultaneously, it is very inconvenient for us to access customer’s environment, which often requires the use of certain type of VPN and related software. As a customer, we want to record centrally all requests and bugs in our own issue tracking tool, and not to collect access data to different systems of our suppliers.
Synchronisation is the solution
The solution usually is that one of the parties, often it is the customer, shall adapt. It means, that this party accepts the impacts of duplicate recording and communication, networks constraints or risk of overlooking the information in a foreign system. But why to be limited by an imperfect solution when there is a more efficient way?
J2J Issue Sync is a reliable application for synchronisation of two and more Jira instances. It can also easily handle synchronisation of more worklogs within one Jira instance. Thanks to a two-way synchronisation of projects, issues, comments and workflow statuses, you always have all information at hand and in one place. At the same time, synchronisation is fully under your control due to an easy setting and clear history of the most important activities.
Test J2J Issue Sync for free at Atlassian marketplace and experience collaboration in Jira without any obstacles.
Try it free