Posts about Confluence

We have an update on our plans to ship breaking changes across Server Products.

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 the spirit of openness, we wanted to share our plans around upcoming breakingchanges across many Server Products.

We are deprecating the old Confluence Ecosystem Support Jira Project on June 25th, 2018.

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.

The latest Confluence 6.9 EAP milestone is available now! EAP releases provide a snapshot of our work-in-progress and give you an opportunity to test and fix your add-ons before the final release.

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.

In this post, we round up all recent Ecosystem news.

Beginning in 2018, Atlassian will be introducing Enterprise releases for Server and Data Center versions of Jira Software and Confluence.

The Atlassian Connect documentation site has been retired and all of its content has been separated by topic and relocated to product documentation.

We have some news for you regarding Confluence Server 6.7 and some visual changes we're making.

Streamline Cloud Deployment with Atlassian tools and Heroku

In this post, we round up all recent Ecosystem news.

This week, we released the first beta for Confluence 6.5 Server. There are changes in this release that may directly affect 3rd-party add-ons.

Atlassian Connect now supports the JWT Bearer token authorization grant type for OAuth 2.0 for JIRA and Confluence Cloud. This allows add-ons with the ACT_AS_USER scope to access resources and perform actions in JIRA and Confluence on behalf of users.

Learn about a small feature of Atlassian Connect, the postInstallPage module.

The Confluence platform team has been building more ways for your Connect add-ons to integrate with and extend search in Confluence. Initially announced at AtlasCamp 2015, we've shipped some awesome new features that allow you to get the most out of content properties.

Did you know you can update 70 pages in less than a minute using a macro-enabled keyboard?In this Tip of the Week we'll explain how you can do this.

The Confluence development team is proud to announce that the first Early Access Program (EAP) release of Confluence 5.9 is now available. There are a large number of API changes and library changes, so now is the time to begin testing and planning new compatibility for your add-on.

We've upgraded to Java 8! Our SDK now requires that you run with JDK 1.8. Given the recent end-of-life of Java 7, our products are on the road to deprecating JDK 1.7 as a supported environment. For you add-on devs out there, you'll need to upgrade your environment to Java 8 and JDK 1.8. If you've run your environment lately and ran into issues such as a blank screen, read on to update and get back into action!

With the release of Confluence 5.7, developers get two new and exciting tools to help them build Confluence add-ons. The REST API has been extended with advanced search capabilities that we're calling CQL (Confluence Query Language) providing great new ways to find the content you're interested in. In addition, content properties now support indexing and querying using CQL - especially handy for Connect add-ons that need to store and query their data in Confluence. I'll walk you through these new features with a simple use case.

You may have noticed a new experience for, which includes changes to how our content in Confluence is displayed. This was an interesting challenge for us as we also have static front-end pages around the site that aren't part of Confluence. These pages are the source for the style applied to the Confluence content, so it was important that we had a way to easily share the layout (templates, Javascript, and styling) between the handful of front-end pages at the Confluence content.