Rate this page:
This page includes release notes and updates for Confluence Cloud app developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from Confluence Cloud.
For updates about changes to the Forge platform, see the Forge changelog in the Forge documentation.
You can also ask questions and learn from other Confluence Cloud developers on the Atlassian Developer Community.
In the developer console, you can now edit the title and description of your app alert, as well as view alert history. You can also see the metrics highlighted when value is below the threshold. For more information, see Manage app alerts.
We added a new endpoint for polling content conversion results asynchronously, and another for directly convert macros to view formats. Together, both endpoints should help mitigate body conversion timeout issues. They can also reduce the number of endpoints required for each macro conversion.
To help you debug your Forge apps, the developer console now displays site-specific information about your app's invocation errors. Just select the invocation errors chart title, or select the More actions (⋯) menu on the chart and View details.
For more information, see Monitor your apps.
To help you monitor the performance of your Forge app, we’ve introduced alerts for when your app’s invocation success rate changes. If your app’s invocation success rate falls below 99%, we’ll send you an email. If you don’t want to receive these emails, you can mute and unmute the alert at any time.
We’re limiting the maximum value of the Get Content operation’s start parameter to 15,000 from Oct 18, 2022. We’re doing this to provide consistent performance from the operation, as our databases cannot currently handle the load put on by high offsets, and are looking into more permanent solutions than the following offered alternatives for the future.
If you use the Get Content operation with a start value over 15,000, and cannot reduce the value, consider using the Search content by CQL operation (/wiki/rest/api/content/search?cql=id!=0) or retrieving content by space instead.
We’ve added a new Forge module, confluence:customContent . This module allows you to register a new custom content type that behaves like the built-in content types, such as page, blog post, or comment. Once a new type is registered, custom content of that type can be created, listed, indexed, and displayed in quick and advanced search results.
For more information, see the description of the custom content module.
Learn more about custom content and use cases here.
EDIT, 17 Aug, 2022: This change was originally announced on August 15th, 2022. However the change was only made effective in production as of August 17th, 2022 (AEDT). Our apologies for any confusion caused.
To help you debug your Forge apps more easily, app logs are now available by default when a user installs your app on their site.
Previously log access was disabled by default. If you needed log access for your app on a user’s site, you had to ask the user to manually give you log access through Admin Hub.
Now log access is enabled by default. When a user installs your Forge app on their site, you will now have automatic access to logs for your app on their site.
Note, apps that are already installed will remain in their current state of log sharing, with log access disabled by default, but we are investigating how to change this.
Disabling access
Users can still manually disable or re-enable log access through Admin Hub. This will remove your access to the logs for your app on their site, including any historic logs that were generated when you previously had access.
To help you when handling logs for your Forge app, we have added new Logging guidelines for app developers. These guidelines outline some best practices to consider when handling logs and determining what data you should, and should not, be logging.
To provide better quality PDF content, we’ve rearchitected the backend supporting the export of Confluence pages to PDF. The change is rolling out to customers progressively and is expected to be with 100% of customers by Sep 9, 2022. This change does not require you to do anything. However, if you perform a PDF export and notice any issues, please report them on CDAC.
PDF exports of Confluence pages produced inaccurate content, leading to many customer tickets. Resolving these tickets one by one was not an effective way of resolving the issues, so a redesign of the backend flow was initiated to find a permanent solution.
In the new backend flow, after Confluence receives an export request, it forwards the request to a chain of microservices that help compose the PDF of the Confluence page and upload the PDF to S3. The result is that PDF exports now look like Confluence pages. Note: Tables are not automatically sized to fit. Instead, the export attempts to match how the user configured the table width.
This exported page is then available to the user in the Download tab as a downloadable link, using an S3 pre-signed URL.
Custom Emojis don’t work
Jira Roadmap Planner doesn’t work
Forge macros won’t work out of the box (we’re working on this)
Nothing. However, please look for errors or inaccuracies in Confluence page PDF exports. If you find something, please raise it in CDAC - https://community.developer.atlassian.com/t/improved-confluence-page-pdf-export-only-backend/60637 , and we will respond. Note that this backend flow is only called when you export a Confluence page to PDF.
10% rollout to customers - Aug 19, 2022
25% rollout to customers - Aug 26, 2022
50% rollout to customers - Sep 2, 2022
100% rollout to customers - Sep 9, 2022
These dates are subject to change should there be any unexpected issues during or before rollout.
The following namespace-level fields (fields on the ConfluenceQueryApi type) and respective return types are now out of beta:
page
pages
blogPost
blogPosts
comment
comments
space
spaces
Check out the docs to explore the API.
This means that GraphQL requests using these fields no longer require the X-ExperimentalApi: confluence-agg-beta header. Also, we will not release any breaking changes to these fields and all types accessible through them without appropriate deprecation notices.
Please note that certain fields on these types may still be marked as beta in the docs (for example, ConfluencePage.comments). These fields will continue to be in beta.
We've added new types and namespace-level fields (fields in the ConfluenceQueryApi type) related to comments:
We've also added new fields to the ConfluencePage and ConfluenceBlogPost types.
To enable clients to fetch comments by ID, we've added these namespace-level fields :
ConfluenceQueryApi.comment(id: ID!): ConfluenceComment
ConfluenceQueryApi.comments(ids: [ID]!): ConfluenceComment
We’ve also added these related types:
ConfluenceComment - interface for all types of comments
ConfluenceFooterComment - concrete type representing footer comments
ConfluenceInlineComment - concrete type representing inline comments
Here’s a sample query for the comments field. It selects different fields based on the concrete ConfluenceComment type that is returned.
It’s important to note the __typename field is required to resolve any interface or union.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
query GetCommentsQuery {
confluence {
comments(ids: ["<id1>", "<id2"]) {
id
container {
__typename
... on ConfluencePage {
id
title
}
}
__typename
... on ConfluenceFooterComment {
body {
storage {
value
}
view {
value
}
}
}
... on ConfluenceInlineComment {
resolutionStatus
}
}
}
}We've added the following fields to ConfluencePage:
author
body
latestVersion
properties
viewer - returns a ConfluenceViewerSummary object that contains data related to the current user (for example, the viewer of the data).
Here's a sample query that requests all the new data:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
query GetPageQuery {
confluence {
page(id: "<id>") {
author {
user {
accountId
}
}
body {
storage {
value
}
view {
value
}
}
latestVersion {
author {
user {
accountId
}
}
createdAt
number
}
properties(keys: ["editor", "exampleProperty"]) {
key
value
}
viewer {
lastSeenAt
lastContribution {
status
}
}
}
}
}We recently launched a new developer support page, which serves as a centralized hub for reporting issues, managing your app and getting support. This page will streamline your experience of getting in contact with us for different areas of support:
Bugs: Report development or Marketplace bugs
Incidents: Report critical issues or breaking changes
App listing: Edit your app or access Marketplace APIs
Accounts and payment: Manage your Marketplace payments and licenses
App migration: Get help with creating a cloud version of your app
Security programs: Apply or adjust your program details
Partner resources: Request access to exclusive partner content
Ukraine support: Request emergency concessions or ask questions
If you have any questions, please get in touch with us via the developer community announcement.
We released the beta version of a major release of atlassian-connect-spring-boot. The release is marked 3.0.0-beta-1. In this release, we’re mainly migrating from Spring Security OAuth 2.x, which reached end-of-life in May 2022, to Spring Security 5.2.x. We’ve also removed certain deprecated methods. For more details, see the list of changes below.
ACSPRING-158: Remove deprecated userKey field in AtlassianHostUser
ACSPRING-159: Remove deprecated publicKey field from AtlassianHost and LifeCycleEvent API.
ACSPRING-160: Remove deprecated findFirstByBaseUrl method from AtlassianHostRepository
ACSPRING-161: Remove deprecated atlassian-connect-* Spring Web MVC model attributes
ACSPRING-162: Use SecurityFilterChain instead of deprecated WebSecurityConfigurerAdapter
ACSPRING-99: Migrate to OAuth 2.0 client support provided by Spring Security
OAuth2RestTemplate from Spring OAuth2 Security 2.x API is removed and replaced by RestTemplate
getAccessToken API is available to request the accessToken for an AtlassianHostUser. This interface is useful if your implementation relies on OAuth2RestTemplate#getAccessToken:
1
2
3
4
5
// before
String token = atlassianHostRestClients.authenticatedAs(hostUser).getAccessToken();
// after
String token = atlassianHostRestClients.getAccessToken(hostUser).getTokenValue();We fixed a bug that triggered a refresh_token is invalid message with status 400 during the OAuth 2.0 refresh grant flow. This occurred when an additional code parameter was provided that matched the format of a JSON Web Token(JWT).
Applications making refresh_token requests that matched the above condition would have seen failures (refresh_token is invalid) to exchange tokens from February 2022 onwards.
To make it easier to track the performance of your shared apps, we’ve added quick-view cards on the developer console landing page, under a new ‘My shared apps’ section. These cards show your shared apps':
Invocation success rate for the last 7 days
Error count for the last 7 days
Last deployment event
To see this change, log into the developer console, and if you’re sharing your app, you will see a card under ‘My shared apps’.
Here’s an example:
If you aren’t sharing any of your apps yet, see Distribute your apps.