Posts about Cloud
Confluence’s SOAP, JSON-RPC and XML-RPC APIs were deprecated with the release of Confluence 5.5 back in 2014. However, we never actually removed them from the product. While they continue to work today, Confluence Cloud will be officially removing these APIs as of March 29th, 2019.
Bitbucket Cloud REST API endpoints and data objects are changing. Certain endpoints and objects will stop being available April 12, 2019.
Announcing that we are using the installed callback to update the base URL of the Jira and Confluence instance a Connect app is installed in. This will be used when a Jira or Confluence site gets renamed as a result of a user request.
The introduction of next-gen projects at the beginning of 2018 changed some Jira Cloud REST API assumptions and core concepts. As a result some apps experienced unexpected behaviour, few apps stopped working in next-gen projects.
We're making changes to improve security that will require the encoding of some characters used in REST API calls.
Knowing what to write about your app can be challenging. The simple act of using a template can help guide your writing and make your documentation better.
We're currently rolling out a new editing experience in Confluence Cloud, which involves some significant changes to Confluence macros and editor. Check out this post for more details.
In order to guarantee stability and performance of Jira, starting on 1 February 2019, we will require that you provide the permissions query parameter in all requests to the Get my permissions (/rest/api/2/mypermissions) resource.
In this post, we round up all recent Ecosystem news.
We just wrapped another successful Atlassian App Week! During App Week Cloud | June 11-15, App Week went back to its Cloud roots and traveled to Portland, Oregon for the first time.
We are deprecating the old Confluence Ecosystem Support Jira Project on June 25th, 2018.
Build end-user awareness of your app, then show them how to use your app competently. This flow shows key steps in the journey vendors control and best practices at each step.
Learn to support admin users post-installation so they successfully announce your app to end users. This flow shows key steps in the journey vendors control and best practices at each step.
The onboarding journey covers two user types; the admin user trying to install and configure apps in the Atlassian suite of products and end users discovering and learning how to use the app. This flow shows key steps in the journey vendors control and best practices at each step.
We recently announced that we are moving away from per-installation shared secrets for apps. Here is a simple verification procedure to make sure your app is ready for the single shared secret migration.
Announcing that we are moving away from per-installation shared secrets for apps to bring Jira and Confluence to use the new Atlassian platform for developers.
The Atlassian Connect documentation site has been retired and all of its content has been separated by topic and relocated to product documentation.
Introducing Cloudtoken, an open source tool to provide access to Federated authentication tokens on the command line.
Sign up to participate in the alpha program for the new Jira Cloud issue view