https://marketplace.atlassian.com/apps/1218450/zendesk-to-jira-service-management?tab=overview&hosting=cloud

Although this issue is against JIRA (Core), the original description was for Service Desk. Now that SD has its own REST API, it might be possible to update my script so that there is less dependency on direct manipulation of the database. This would be particularly useful for comment privacy status as that was one of the biggest challenges to work around in the database.

So if anyone is using the script and wants to update it, feel free: https://bitbucket.org/pcolmer/zdtosd-importer.

Otherwise, I'll try and update it if I get the time

ainacio The Python script can be used on cloud instances if you turn off the direct MySQL support. It should be noted that if you do that, the script is unable to import private comments (because there isn't a REST API to set the privacy in Service Desk) and it is unable to set the dates on issues or who submitted comments. In the case of the latter, the script works around the problem by adding the commenter's name at the start of the comment.

It isn't how I'd like the script to stand but given the limitations of the API available from Atlassian, it is the best I could manage. It handles attachments, creating accounts as required, etc.

Hi Thomas, There is a work around for this.
During our testing we uncovered that since the csv/json importers are built specifically for Jira, there are some major limitations when importing SD tickets.
One of which is that the importer does not provide an option for filling in the Customer Request Type field. This field is necessary for all SD issues. In order for imported SD issues to appear on Requester Portal and for requester to receive notification regarding these issues, you need ot perform a Bulk Change on all imported issues, and give the Customer Request Type field a value.
This is a work around and not a solution. Also it still does not solve the Private/Public comment issue that s a deal breaker for us.
I believe the best course of action here would be for Atlassian to update the current importer to support SD imports.

Alan, Thanks for the advice regarding importing tickets and not having them visible to the requesters portal is a deal breaker for us. I'm currently evaluating a swtich to JIRA Service Desk as the SLA functionality is spot-on what we need.

Sorry.. was signed into the wrong account!

Yes, this would be for self hosted systems.

-Luca

Luca, I'm guessing this would only work for on premise installations?

Hey folks,

We had the same issue, so my manager wrote a script to resolve the issue - it worked really well for us. It can only be used with MySQL databases though as that's what we use. Hope it helps

https://bitbucket.org/pcolmer/zdtosd-importer

Ta,
Luca

I just looked at the cost of zendesk plan we're on compared to the price of integrated JIRA+SD+bitbucket and possible use of capture as well. I'm writing up a proposal for my boss to make the move (plus I upvoted asciidoc)

We will save buckets of cash with Atlassian but migration of existing tickets is a must and he'll nix the move if we can't migrate smoothly and seamlessly