Hello, I am quite a novice user of Jira, and have been confronted with the following situation described below. There are two companies, company A and company B. Company A makes a product for company B. Company B uses the product, and puts their error descriptions / problem reports into their Jira system as tickets. Company A receives the error description and set a ticket in company A's Jira system. What the two companies would like to have is an automatic linkage between the two Jira systems: * when company B generates a new ticket, and wants to share this ticket with company A, there should be an automatic signal (for example an automatic e-mail) sent to company A + company A should be able to read this ticket. But only this ticket, not all the tickets of company B * when company A makes an update to the corresponding ticket in Company A's Jira, an automatic signal should go to company B that there is an update at company A's side Is this linking with automatic updates possible? Thanks for your support!

Hey @Istvan Fay I gave a talk last year about cross-company collaboration scenarios in Jira last year. It mentions 5 ways how you can collaborate: * Use Email for the exchange & manual update in your Jiras * Allow the users of one company to access the other Jira and use permissions/issue security schemes/etc. * Use a shared Cloud instance for this project * Share issues externally (like a dropbox link) via an external share app from the Atlassian Marketplace * Sync issues with the other instance via an issue sync app from the Atlassian Marketplace Here's the full talk: https://www.youtube.com/watch?v=25mdkFFQ4Gg Let me know if you need further help. Cheers, Matthias. PS: I'm part of a team behind the Backbone Issue Sync - one of these issue sync apps.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Giving links to Jira tickets from another Jira

Istvan Fay

Hello,

I am quite a novice user of Jira, and have been confronted with the following situation described below. There are two companies, company A and company B. Company A makes a product for company B. Company B uses the product, and puts their error descriptions / problem reports into their Jira system as tickets. Company A receives the error description and set a ticket in company A's Jira system. What the two companies would like to have is an automatic linkage between the two Jira systems:

when company B generates a new ticket, and wants to share this ticket with company A, there should be an automatic signal (for example an automatic e-mail) sent to company A + company A should be able to read this ticket. But only this ticket, not all the tickets of company B
when company A makes an update to the corresponding ticket in Company A's Jira, an automatic signal should go to company B that there is an update at company A's side

Is this linking with automatic updates possible?

Thanks for your support!

Accepted answers

Trudy P Claspill

Hello @Istvan Fay

Welcome to the Atlassian community!

For Company A and Company B:

- What is the hosting type for their Jira instances? Are they self-hosted (Jira Server/Data Center) or Jira Cloud hosted?

- In what type of project are the tickets being created for each company? Are the tickets in Jira Software projects or Jira Service projects or Jira Core/Work Management projects?

Matthias Gaiser _K15t_

Hey @Istvan Fay

I gave a talk last year about cross-company collaboration scenarios in Jira last year. It mentions 5 ways how you can collaborate:

Use Email for the exchange & manual update in your Jiras
Allow the users of one company to access the other Jira and use permissions/issue security schemes/etc.
Use a shared Cloud instance for this project
Share issues externally (like a dropbox link) via an external share app from the Atlassian Marketplace
Sync issues with the other instance via an issue sync app from the Atlassian Marketplace

Here's the full talk:

https://www.youtube.com/watch?v=25mdkFFQ4Gg

Let me know if you need further help.

Cheers,
Matthias.

PS: I'm part of a team behind the Backbone Issue Sync - one of these issue sync apps.

All comments

Trudy P Claspill

Hello @Istvan Fay

Welcome to the Atlassian community!

For Company A and Company B:

- What is the hosting type for their Jira instances? Are they self-hosted (Jira Server/Data Center) or Jira Cloud hosted?

- In what type of project are the tickets being created for each company? Are the tickets in Jira Software projects or Jira Service projects or Jira Core/Work Management projects?

Istvan Fay

Hello Trudy,

thanks for the fast response!

They are Jira Cloud hosted, I believe
Sorry, how can one decide which version of Jira is used there?

Istvan Fay

From the attended usage point of view, I would say it is Jira Service Management: we would like to use it as an error ticketing system

Istvan Fay

The cooperation as described in Wikipedia under Networked Help Desk API (Networked Help Desk - Wikiwand) is pretty much the way how we would like to cooperate.

Is the understanding correct that Networked Help Desk API is already built in into Jira, so when we have separate Jiras, but turn the API in both sides on, this automatic exchange of update is solved?

Matthias Gaiser _K15t_

Hey @Istvan Fay

I gave a talk last year about cross-company collaboration scenarios in Jira last year. It mentions 5 ways how you can collaborate:

Use Email for the exchange & manual update in your Jiras
Allow the users of one company to access the other Jira and use permissions/issue security schemes/etc.
Use a shared Cloud instance for this project
Share issues externally (like a dropbox link) via an external share app from the Atlassian Marketplace
Sync issues with the other instance via an issue sync app from the Atlassian Marketplace

Here's the full talk:

https://www.youtube.com/watch?v=25mdkFFQ4Gg

Let me know if you need further help.

Cheers,
Matthias.

PS: I'm part of a team behind the Backbone Issue Sync - one of these issue sync apps.

Istvan Fay

Hi Matthias,

thanks, that was a avery good presentation, help to put some issue on their places!

BR, Istvan

Syed Majid Hassan -Exalate-

Hi @Istvan Fay

This is Majid @ Exalate.

As has been pointed out, issue synchronization apps such as Exalate, specialize in performing this Jira to Jira collaboration between two independent instances. In our experience, the most important factors to consider in such cases are security, granular control over data and autonomy of both sides. You can read up about how Exalate excels in cross-company collaboration but keep these factors as the driving force behind our solution.

Hope it helps.

Happy syncing!

Thanks

Majid

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-work-management