We currently have two instances of JIRA, one for ITS and one for Engineering. The company now has joint development for specific projects between ITS and Engineering. What we would like to do is configure JIRA so that cross comunication can occur over different Projects across both instances of JIRA residing on different servers.
Can you define better what you mean by cross communication since there are multiple interpretations and how much effort/cost you can put into your solution? For example, is the ITS and Engineering workflows serial or parallel to each other? Are their workflows the same or different? Can you get away with each group just viewing each others states? You cannot share databases between Jira instances today, but can you invest time/cost into writing to a third database which is designed for concurrent/parallel access?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs