If you hire an external development team, you have to pay for their work (according to the MD rate), but you are also usually asked to provide them with your Jira licenses, which results in additional costs for your company. We tried to find another way, so we started to synchronize Jira issues for these external development teams between the company's Jira and the external team’s Jira using Backbone Issue Sync for Jira.
There are many possibilities, how to use this app. You can connect the L1 customer support project in one Jira with the L2 and L3 customer support project in the Jira of an external company. Or the product owner can communicate with development teams this way. Alternatively the project manager distributes the tasks between many contractors to their Jira instances.
Our customers usually use this app for synchronization between more Jira instances (1:N), there’s a product owner on one side and the development and testing teams on the other side (agile development team).
If we do not use these integrations, we would see a steep increase in administration. We would also lose transparency. We would end up forcing users to access the multiple Jira and duplicate information. This would result in frustration and errors, which is unthinkable in many cases today.
Thanks so much to everyone who joined for our July Appy Hours! Product and project management presenter highlights Checkout - Procurement and asset manager, presented by @Vincent Mutambuki ...