How do I push a new JIRA Key to SF when a task is moved in JIRA?

[Sue Wilson]

We have a task in JIRA under Project A.  The task is moved to Project B, which changes the issue key from, let's say, PA-123 to PB-456.  Our integration is set up to push the JIRA Key to SF, BUT if a task is moved in JIRA, the new Key is not updated on the SF Case.  Any ideas how to accomplish this push to the new Key and, if possible, maintain the old Key value for reference?

[Diana_Architect_ZigiWave · Accepted solution]

@Sue Wilson ,hi. Did you manage to find a solution? 

Let me propose a solution that might help you. My name is Diana and I am a solutions architect at ZigiWave. Our no-code integration platform ZigOps will help you connect Jira and Salesforce in a matter of minutes. It allows the transfer of default and custom fields between the systems and syncs them in real-time. It connects the systems bi-directionally, so a change in one of the systems will immediately be present in the other.

ZigiOps reads the schema dynamically and can transfer any field. If you want to see how it works in action: book a technical demo. 

[Sue Wilson]

@Diana_Architect_ZigiWave hi & thank you for your response.  Yes, I found a solution.  We already have a Jira to/from Salesforce connection.  The problem was when the issue key changed in JIRA, the updated value was not being updated in SF as expected.  This confused/concerned the user due to the mismatch.  We found a way to extract the issueid, append that to complete a url and pass that to SF.  Works like a charm and our internal customer is happy with the result.

[Diana_Architect_ZigiWave]

@Sue Wilson happy to hear that. :)