A jira instance for working with multiple external organizations

Dear @saltypotato 

I work for Exalate.

Managing multiple Jira instances can be challenging. Your idea of consolidating into a single Jira instance is solid, but keeping everything in sync across different companies’ Jira systems might still be tricky.

 You could explore a tool like Exalate, which allows seamless bi-directional synchronization between separate Jira instances. It would let you maintain visibility over all backlogs while enabling each software company to work in their own Jira environment. This might be a more straightforward and scalable approach.

Thank you.

Kind regards,
Mathieu Lepoutre

Disclosure: I'm the founder of Ticketize.it, a Jira-to-Jira sync tool, so I'm biased; weigh accordingly.

Late to this, but the thread still ranks for the question and your two follow-ups never got answered, so for anyone arriving from search:

Your conclusion was probably the right one. One instance, a project per software company, permissions doing the isolation, is genuinely the better architecture when the vendors are willing to work in your site. Less machinery, one index, boards and JQL that just work. Don't let anyone talk you out of that in order to sell you something.

On the GitLab/GitHub question: yes, that still works. Each supplier connects their own GitLab/GitHub to whichever Jira they actually work in, and that link is configured per site. It is not affected by how many Jira instances exist or whether anything is synced between them. If the suppliers work in your instance, they connect their repos to your instance, and the development panel shows their branches and pull requests on your issues.

On why the pricing surprised you, which is the part nobody answered: most sync tools bill per connection. Exalate's entry plan is roughly $85-100/mo per integration, capped at 25 active items in sync. Four suppliers means four integrations, so $340-400/mo before you have synced a hundred tickets. So to answer directly: yes, you would be paying per instance pair, not once. That is not you being cheap, it is a pricing model that charges for fan-out, and yours is a fan-out shape.

One more trap worth knowing about Marketplace apps in general: Atlassian bills them on your site's total user count. A 500-seat org syncing 20 tickets with a single vendor pays for 500 seats. That kills more of these projects than the sticker price does.

If syncing ever does become unavoidable, because a supplier will not work in your site or a contract requires the data to stay separate, the realistic options are Exalate (scriptable, handles Data Center, priced per integration), Backbone Work Sync (per user), Getint, and mine, Ticketize.it, which is $0-29/mo flat no matter how many supplier Jiras you connect, with no item cap: https://marketplace.atlassian.com/apps/109949502/ticketize-it

The caveat that matters for your case: you mentioned your suppliers are a mix of Cloud and Data Center. Mine is Jira Cloud only, so it would cover the Cloud subset and nothing else. For the Data Center suppliers you would still need Exalate or a script. Better to say that plainly than have you discover it after a trial.

Hello @ saltypotato,

Yes, your idea is feasible and can be implemented with Jira. Here’s how you can achieve it:

Set up a Jira instance and create separate projects for each software company. This will help you manage and track their work individually while maintaining an overall view.

Syncing data between two Jira instances can be achieved using several methods, depending on your specific needs and the tools available. Tools like Exalate and Backbone Issue Sync are popular for syncing data between Jira instances.

may I know whether you are using Jira cloud or data center.