Can I create an issue in one server when another issue is created in another server?

[raulmercadox]

The client has a Jira Cloud, and my company has a Jira Server. The client does not want to create issues in my Service Desk Product. He wants to continue using its Jira Cloud. Is there a way when the client creates an issue in its Jira Cloud to automatically create the same Issue in our Jira Server?

Thanks,

[Florian · Accepted solution]

Not by default. But with an Automation for Jira this should be feasible.

Preconditions:

- Your server needs to be accessible from the outside world

- There should be a dedicated user account on your side for this task

- The external partner should have an automation rule that replicated the issues over REST

Things to consider:

- Do you want an exact copy or can you live with basic information (issuetype, summary, description) without custom fields. 

- What happens when your server is down for maintenance? Maybe some queuing system should buffer the messages. 

- Is it enough to have an initial replication when a new issue is created or do you need constant updates let’s say when an issue is transitioned. In this case you need to rebuild the complete workflow and you need to have some customfield to virtually link your local issues to the remote issues. Usually the local issued get new keys. 

- Do you need a one way or a two way interface. Two ways is usually much more complex as you have to ensure who is the master when colliding changes are made. 

I would not go this road on my own without external consulting.