Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Salesforce connector : How to keep links to Jira alive when moving to cloud ?

Edited

Hi

We are migrating from Jira server to Jira cloud. 

I am concerned with the salesforce server which is linked to Jira using until now Jira Server For Salesforce connector. I have installed now Jira Cloud For Salesforce package.

Salesforce cases are currently linked to Jira server objects (bugs, epics...).
In order to keep the links fonctionnal after migration to Jira cloud, what must be done in Salesforce?

We have changed the triggers and layouts in order to use the new objects of the package JCFS instead of JSFS. That's ok.


Question is : I suppose that salesforce cases contains a Jira reference to Jira server bugs in some fields from JSFS package. How to migrate that to a Jira Cloud reference (JCFS Package fields), so that synchronisations will continue to work when the cloud is active? Do we have to copy some data from an old field to a new field in Salesforce, or just installing the JCFS package is enough?

Thanks
Frederic Provot

1 answer

Dear @Frederic Provot

 

My name is Christophe and I am a solution engineer @ Exalate.

You can use Exalate for various use cases from migration to a perfect bi-directional synchronization between Salesforce & Jira.

With Exalate you don't have to worry about changes being made on each side because the solution boasts a unique decentralized approach.

You can easily fetch Account and contact information, as any related object from Salesforce to a Jira ticket, and vice versa while providing full autonomy to each side of the connection.

You also can automate this process via triggers so you don't have to worry about manual work in the future.

Please feel free to book a demo to see how Exalate fits your use case or explore how the solution works here

 

Thank you in advance and kind regards,

Christophe De Beule

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events