How to use Jira's workflow to trigger a sync up ticket?

[allenhsieh]

Hi guys, 
I have a situation that we like to use Jira's workflow or status to initiate sync up to a desired receiver project or company.  

Use Case:
3 platforms to sync up together/
A. Jira Software/Cloud - B. Jira Software/Cloud - C. Jira Service Desk/Local

Source Project - A
Receiver Project - B and C

Pluggings:
Exalate

Case one - Source project A uses workflow to assign a ticket to the receiver B while the receiver C can't see this ticket (compliance concerns). 

Case two - Source project A uses workflow to assign a ticket to the receiver C while the receiver B can't see this ticket (compliance concerns). 

Can any experts or use cases out there to shed a light on this particular use case?

I kept asking Exalate customer service about it and they were telling me this is the place where my special use case will get some directions or even a practical solution. 

I really appreciate to whom seeing this question and have some good tips and thank you in advance for leaving a mark here.

THANK YOU~

[Jose Lobo (Solutions Architect at Exalate)]

Hi  Allen,

This can be done by creating 2 connections with one trigger for each of them


Example 1:

Connection: AtoB
Trigger: AtoB

In this trigger AtoB you can say for example: status = "Sent to company B" 
And sync with the connection AtoB



Example 2:

Connection: AtoC
Trigger: AtoC

In this trigger AtoB: status = "Sent to company C" 
And sync with the connection AtoC



Let me know if this answers your questions 🙂

[AllenH]

Hi Jose, 
Thank you for the tip, here I post a picture to explain it a bit more. 
My question is to use workflow to trigger sync to a specified receiver:

For instance:
If I choose Assigned to 2nd support (Project B), the ticket will be generated and sync up to project B, not Project C. 

If I choose Assigned to Asia Support (Project C), the ticket will be generated and sync up to project C, not Project B. 

[Jose Lobo (Solutions Architect at Exalate)]

Hey Allen,

The destination project is set on the connection configuration

You could set up two connections, one per project destination

Then, create a trigger associated with each connection.

Connection 1

Destination Project: Project B

Trigger 1:

Status = "Assigned to 2nd Support" (with the correct syntax obviously)

Connection 2

Destination Project: Project C

Trigger 2:

Status = "Assigned to Assia Support" (with the correct syntax obviously)

[AllenH]

Hi Jose, 
It worked!

Thank you so much~