This would be especially helpful when migrating into Salesforce Service Cloud from some other ticketing system that had a JIRA integration/function and thousands of client-ticket-to-JIRA-ticket links in place already.
If you could export the associations from the other system into a .csv file and then use this "importer/associator", it would save countless hours of clerical work.
Dmitrij Marcinkevic commented
23 Dec, 2021 12:04pm
Workaround could be done using API callouts and batch class, but if more than 100 Jira issues should be associated to the same record, then you will reach callout limits.
Megan Callaghan commented
29 Jun, 2021 04:05pm
Does anyone have any workarounds? We created a separate text field in Salesforce so that we could track / report on it a little more easily but curious what others have done for this. thanks!
Chris Perry commented
25 Feb, 2021 09:11pm
My company is about to migrate to JiraCloud and we stand to lose 15,000 associations from the Salesforce connector. Please implement a CSV association importer.
Lindsey Hogan commented
15 Sep, 2020 03:53pm
In the migration to JiraCloud and using the Salesforce connector, i need a way to mass associate issues via .csv. In this use case, I want to be able to only associate open issues. This is still hundreds of associations.
Guest commented
15 Nov, 2019 08:40pm
We are migrating our bug tracking system to Jira and considering using the SF/Jira Connector. We need a way to mass associate Jira items to Salesforce Cases during this migration. Please implement this.
Azwandi Mohd Aris
This would be especially helpful when migrating into Salesforce Service Cloud from some other ticketing system that had a JIRA integration/function and thousands of client-ticket-to-JIRA-ticket links in place already.
If you could export the associations from the other system into a .csv file and then use this "importer/associator", it would save countless hours of clerical work.
Workaround could be done using API callouts and batch class, but if more than 100 Jira issues should be associated to the same record, then you will reach callout limits.
Does anyone have any workarounds? We created a separate text field in Salesforce so that we could track / report on it a little more easily but curious what others have done for this. thanks!
My company is about to migrate to JiraCloud and we stand to lose 15,000 associations from the Salesforce connector. Please implement a CSV association importer.
In the migration to JiraCloud and using the Salesforce connector, i need a way to mass associate issues via .csv. In this use case, I want to be able to only associate open issues. This is still hundreds of associations.
We are migrating our bug tracking system to Jira and considering using the SF/Jira Connector. We need a way to mass associate Jira items to Salesforce Cases during this migration. Please implement this.
CASE #85368