Jira to Jira sync between two companies
IssueMesh keeps a Jira Cloud project of yours and one of your partner's in sync in near real time - issues, fields, statuses, comments and attachments. Each side decides what leaves its Jira and where incoming values land.
For vendors and their customers, clients and subcontractors, support desks and development teams on another site. Your partner can use IssueMesh Free at no cost.
How it works
Three steps, all inside Jira. No shared accounts, no scripts, no consultants.
-
Install
A Jira admin installs the IssueMesh app on each Jira Cloud site, names the organization and enables the spaces that may be synchronized.
-
Pair
A space admin sends a pairing request to the partner's space. The partner's space admin accepts it.
-
Choose what to share
Each side sets up its own half - what it sends and what it receives - or takes the recommended setup in one click. Synchronization starts as soon as both halves fit.
The IssueMesh app is an Atlassian Forge app. When an issue changes in an enabled space, it tells the IssueMesh Hub which issue changed - never its content. The Hub reads the issue with the app's access, keeps only the fields the sending side shares and writes the difference into the other Jira.
Synchronization is state-based: a missed or duplicated event never causes a wrong or duplicated change, and anything missed is caught up within about ten minutes.
Each side stays in control
A pairing has two halves owned by different organizations. Neither side can push a configuration onto the other or read its setup.
You decide what leaves
- Which of your fields are shared, and under which name
- Which issues take part - by issue type and an optional JQL filter
- Whether public comments and attachments go along
Your partner decides what enters
- Which of their fields each shared value is written to
- How values and statuses map to theirs
- Whether new issues are created, and with which type
Your partner sees
- Your organization name and site address
- The shared fields you send: names, kinds, values
- The content of the issues you share, as you shared it
- People in shared people fields, by display name
Your partner never sees
- Your other spaces, issues and pairings
- Your field names, IDs, screens and workflows
- Fields you do not share, and internal comments
- Anyone's e-mail address
What IssueMesh synchronizes
Everything two teams need to work on the same issue from their own Jira.
Fields, values and statuses
Summary, description with formatting, priority, labels, due date, status, assignee and custom fields - text, number, date, select, multi-select, checkboxes, labels and user pickers. Values are mapped by name, so your "Blocker" and their "P1" can mean the same.
Comments and attachments
Public comments with author and organization, including replies and edits. Internal comments never leave. Attachments up to 100 MB per file, streamed from Jira to Jira.
New issues on both sides
The receiving side decides whether new issues are created, with which issue type, and which fixed values fill the fields its Jira requires.
Existing issues, matched first
Issues from before the pairing are matched with their likely counterparts. The receiving admin pairs, imports or ignores each one - nothing is duplicated.
Pause, resume and resync
Each direction can be paused and resumed on its own; changes made in between catch up within minutes. An Activity tab per pairing and a panel on every synchronized issue show what happened.
Guided setup, no scripts
Space admins pair and configure inside Jira, or take the recommended setup in one click. A problem is shown to the side that has to fix it, with a button to the right place.
Editions
Both editions have every feature. They differ only in how many pairings and issues a site can have with partners on IssueMesh Free.
IssueMesh
Price on request
- Every feature
- Unlimited pairings with sites on IssueMesh
- Unlimited pairings with sites on IssueMesh Free - your partners pay nothing
IssueMesh Free
Free
- Every feature
- Unlimited pairings with sites on IssueMesh
- With another IssueMesh Free site: 1 pairing per site, up to 100 synchronized issues
One license covers the whole relationship. A vendor on IssueMesh can pair with any number of customers, and each customer installs IssueMesh Free without a budget or a procurement process.
Security and privacy
- Nothing synchronizes until a Jira admin enables a space and a space admin chooses what it shares.
- Every request from the app to the Hub is signed by Atlassian; the Hub checks the installation and, for every setting, that the person really administers the space.
- App access tokens are stored encrypted, each with its own key, and can only reach their own site.
- The Hub keeps the last synchronized values of shared fields to detect changes - not comment texts, not files.
Frequently asked questions
Does my partner have to pay?
No. When your site runs IssueMesh, your partner installs IssueMesh Free and gets every feature at no cost, with any number of pairings and issues. Only between two IssueMesh Free sites is there a limit: 1 free pairing per site with up to 100 synchronized issues.
Which Jira products are supported?
Jira Cloud, including Jira Service Management and Jira Software spaces on the same or different sites. Jira Data Center is not supported.
Does IssueMesh store our comments or attachments?
No. Comments are copied directly into the other Jira; the IssueMesh Hub keeps only their IDs and a fingerprint to avoid duplicates. Files are streamed from one Jira to the other and never stored.
Can our partner see our fields, people or internal comments?
No. The partner sees only the shared fields you chose to send, under the names you gave them. Your field configuration, workflows, other issues, e-mail addresses and internal comments never leave your site.
How fast is synchronization?
Near real time: a change usually reaches the other Jira within seconds. Anything missed - for example while a Jira was unavailable - is caught up within about ten minutes.
What about issues that existed before the pairing?
They are never copied blindly. IssueMesh lists likely counterparts on the other side, and the receiving admin decides to pair, import or ignore each one.
Connect your Jira with your partner's
IssueMesh is installed through an installation link while it is not on the Atlassian Marketplace yet. Tell us about your site and your partner, and we get you started.