Rate this page:
This page includes release notes and updates for Jira Cloud app developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from Jira Service Management Cloud.
Go to our developer community to ask questions. You may also be interested in the What's New blog for Atlassian Cloud where details of major changes that affect all users of the Jira Cloud products are announced.
On January 18, 2023, we'll be extending the length of API tokens for Atlassian accounts, API keys, and Repository Access Tokens. This ensures new tokens and keys generated after this date are more secure and reliable. Tokens and keys created before January 18, 2023 won’t be affected.
In the developer console, you can now edit the target value of your Forge app alert. Previously, the alert was set at a target value of 99%. Now you can choose from a number of values between 99% and 60%.
For more information, see Manage app alerts.
The full-page issue create experience will be retired for all Jira Cloud customers over the next 6 months. Although there is no formal API for the full-page issue create experience, it’s possible that some apps may be relying on it and will need to be updated. For more information, read this community post.
The Jira/Confluence Cloud First Releases for Ecosystem initiative has been renamed to Developer Canary Program and now includes an app to provide self-service capabilities for developers.
For more information on how to get started with the program, see the Developer Canary Program documentation.
To access the Developer Canary Program app for:
Jira Cloud, visit the app in Marketplace at Developer Assistant for Jira.
Confluence Cloud, visit the app in Marketplace at Developer Assistant for Confluence.
Added Germany as supported realm for Connect data residency.
Today, we are happy to announce the launch of the Early Access Program (EAP) of data residency realm migration for Connect apps. This EAP release includes a new realm migration service and associated APIs, which will enable you to start integration and testing to support migration of app data to match the parent product realm.
To quickly identify the current state of your Forge apps, the developer console now displays values, as well as charts, for each metric. For more information, see View app metrics.
To help you debug your Forge apps, the developer console now lets you group your metrics by app version. Each chart now has a Group by dropdown menu, with the option to select Version. For more information, see Monitor your apps.
In six months, we will delete this template key from JSM’s create project API:
com.atlassian.servicedesk:simplified-general-service-desk
The key will be deprecated as the template itself has been removed from the product. It can no longer be used by our customers to create new projects.
Going forward, please use one of the other, similar template keys outlined in our documentation, such as:
com.atlassian.servicedesk:simplified-general-service-desk-it
com.atlassian.servicedesk:simplified-general-service-desk-business
In six months, the template key will be deleted completely and no longer usable by the create project API.
When a user installs your Forge app via installation link, we now display a link to your app settings page on the installation success popup:
The link will only show to users if you have an app settings page for your app. If you don’t have an app settings page, you can add one by including either the Jira admin page or Confluence global settings module in your app’s manifest.yml file.
Please note:
The installation success notification can currently only display one link to a single app configuration page. If the confluence:globalSettings or the jira:adminPage have both useAsConfig or useAsGetStarted pages specified, then only the link to the useAsConfig page will be displayed.
The link to an app’s configuration page will only be displayed if the direct distribution link is generated for a single product. For example, the link to the configuration page will not be displayed if an app is installed on both Jira and Confluence, but it will be displayed if the app is installed on only Confluence.
This feature isn't available for Compass apps.
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.
Added Jira Service Management portal request create property panel module, which enables apps to save arbitrary data during request creation as Jira issue properties.
Run npm install @forge/ui@latest on the command line in your app directory to install the latest version of the UI kit.
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.
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.