As JSD is built on the JIRA Platform, many of the existing JIRA platform APIs are well-suited for building integrations and add-ons for JSD.

At Atlascamp in May 2016 we launched JSD-specific APIs for creating requests on behalf of customers, pulling out detailed SLA metrics and various UI integration modules in both the agent interface and customer portal.

You can check out our latest developer docs on: http://developer.atlassian.com/service-desk

Some of you have asked for JSD-source code access. While this is something we are aiming to provide in the future, we do not recommend hacking the source code as it puts your integration on an unsupported path. If you still feel you need source code access, please vote for JSD-397 and watch it for future updates.

If you have requests for specific API or would like to vote for / give feedback on proposed API, check out the JSD Ecosystem project on: https://ecosystem.atlassian.net/projects/JSDECO

Totally agree - we need to source code to have good integration and multi-version support for Service Desk in our add-ons, which is something Atlassian can only benefit from. As Igor points out, some of our add-ons would not exist if we did not have access to the source code.

All of the above. Official integration points, source code etc. Unfortunately this is becoming more and more spread throughout the products with less integration capabilities being made available.

I've written a couple of integration points but not able to publish them because of support reasons (if the integration points aren't there official - then I can't support the usage of them).

The 'opening' should not be only in terms of sharing the source code. I would be glad to have some well documented integration points into JSD .... provided that they exist.

Igor you are totally right. Without source the Atlassian ecosystem will grow much more slowly.

Atlassian JSD people, please add an update about this

I would add, from my point of view, for plugin developers it wasn't so much about "trust building", but more about providing ultimate documentation about the product. Many major plugins wouldn't exist if JIRA / Confluence sources weren't available.

We had this issue multiple times with customers. I do not understand, if Atlassian has changed its policy. The availability of source codes has been a trust building upside of Atlassians product offering. I would feel bad, if that was abandoned now.