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 Cloud Platform.
For updates about changes to the Forge platform, see the Forge changelog in the Forge documentation.
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.
In the upcoming quarter we plan to update our Connect data residency service to support realm persistence.
Realm persistence allows partners to save time and avoid negative customer experience by helping to ensure that customer app pinning does not move between realms upon reinstallation. With realm persistence, app pinning will only move when the app is reinstalled outside of a defined duration or when otherwise requested to move by the customer through the realm migration service.
If you are waiting to implement data residency for your Connect app due to realm persistence concerns. Keep an eye out here in the change log for updates in the coming weeks.
We’re pleased to announce an important security update for webhooks. Users now have the ability to secure webhooks with a new
secretfield. This enhancement applies to webhooks created through Jira Administration or via the REST API.
secret is added to a webhook, it is utilized to generate an HMAC (Hash-based Message Authentication Code) signature. This signature is then included in the request header, ensuring the integrity and authenticity of the webhook payload.
For a comprehensive guide on implementing and understanding this security feature, please refer to the Secure admin webhooks section.
Rollout: progressive roll-out by request. in progress
The extended deprecation period for Lenient URL path processing for OAuth 2.0 requests has now expired. This change will be rolled out progressively over the coming week.
We are deprecating the onHover parameter for Connect inline dialogs.
The current behaviour provides users an inconsistent interaction pattern for opening inline dialogs between different apps. We have observed low usage of this parameter, and it can contribute to inconsistent behaviour opening and closing dialogs.
The previous documentation for this parameter incorrectly stated that
onHover would trigger the dialog on a hover trigger instead of a click, rather, it was in addition to a click.
Once this deprecation is completed, only clicks will open inline dialogs.
Our data shows that this parameter has very low usage so we do not anticipate any significant disruption from this change.
We are rolling out an update to Confluence’s page creation & editing experience. The Confluence sidebar (content tree) and top navigation will now be visible while editing to make it easier for users to understand where they’re creating, and reduce the degree of context switching between editing and viewing pages. This is currently rolled out to a portion of customer sites, and is continuing to roll out to all customers over the next week.
There are a couple of newly possible cases with Extension points we’d like to highlight:
By displaying the space sidebar while editing, it’s now possible for a Confluence user to see and interact with Space Sidebar Web Items while in the editing experience.
Furthermore, web items available in the editing experience - the Edit Page Precursor Web Item, Editor Save Bar Panel, and web-panels associated with
atl.general - are slightly shifted due to the updated toolbar experience & presence of an expanded or collapsed sidebar next to the editor.
Note: This feature is not the same as as the “Live-Edit Pages EAP” that has been previously mentioned in the changelog. This feature applies to the editing experience for both standard published pages and Live-Edit Pages. Live-Edit pages are only available to a small set of early access customers and vendors that have chosen to opt in.
Learn more in our community post here.
A Data Security Policy section for each API now indicates whether the API is exempt from app access rules or not. You can find this in the REST API references pages, and the downloadable OpenAPI specifications associated with them, for:
You can use this to prepare your apps prior to General Availability of the app access rule functionality. It is scheduled for customer release by the end of Q1, 2024 (31 March).
We recommend that you:
Carefully review the app access rule details for the APIs your app uses
Consider how you want your app to behave when APIs that are subject to being blocked return no data, or fewer rows of data, due to an app access rule.
For more information on how app access rules may impact app functionality and how to manage the customer experience, see the https://developer.atlassian.com/cloud/jira/platform/data-security-policy-developer-guide/ .
To prepare your apps for the upcoming General Availability of app access rule functionality, we’ve published documentation on new data security policy events. Customer release is scheduled for the end of Q1 of the calendar year 2024.
The new events will be available for early access by developers in late February, 2024. We’ve published this documentation in advanced so you can start preparing your apps to receive the event notifications when appropriate.
We have updated the following guides with information about the new data security policy events your app can subscribe to:
Additionally, a new https://developer.atlassian.com/platform/forge/events-reference/data-security-policy-events/ reference page has been added for Forge app developers.
We have introduced a new webhook for the
issuetype entity in Jira Cloud. This webhook is designed to trigger on create, update, and delete events, enhancing the functionality and flexibility of our system.
These events are named
issuetype_deleted. This means that any time an issue type entity is created, updated, or deleted, the corresponding webhook event will activate, allowing for real-time tracking and response.
We’re pleased to announce the preview availability of adopting Forge from Connect.
Existing Connect apps now have a simpler, automated and incremental pathway to adopt Forge capabilities. This release includes:
Automated tooling to support the conversion from Connect to Forge
Support for immediate version updates of Forge apps containing
Increased compatibility for the types of
connectModules that can be declared within a Forge manifest
We’ve added 4 new APIs that enable you to get, update, and delete the default classification level on a project, as well as to get the list of all classification levels.
As announced in CHANGE-1220: Rename the issue screen default tab for REST APIs and Jira admins, we have now renamed the default tab in an issue screen from "Field Tab" to "General" for the Jira admin interface and REST APIs.
This change announced in November will take effect from 27th February 2024 with a progressive rollout. It only applies to Premium and Enterprise instances of Jira Software Cloud.
To further improve Plans for Jira Software Cloud, team-managed projects will no longer restrict parent association for hierarchies above epic to the same project. The restriction on lower hierarchy levels (epic to stories and stories to subtasks) remains unchanged.
This is a behavioral change on APIs that write and read parent issue associations. As a result, parent issues of epics in team-managed projects can now be from other projects.
When we roll out this change, it will then become possible to set the parent issue of an epic in a team-manager project to be an initiative issue of a company-managed project. See the below diagram for more details.
A new version of Atlassian Connect Express (version 10.0.0) has now been published which supports new ngrok configuration options. We recommend upgrading to this version if you are utilising automatic registration in ACE.
Please switch to using the new field
ngrok in your
credentials.json, as detailed in the README.
A new version of Atlassian Connect Express (version 9.0.0) has now been published which implements
@ngrok/ngrok. We recommending upgrading to this version if you are utilising automatic registration in ACE.
Please note that a new field
ngrokToken is required in your
credentials.json file to support this change, as detailed in the README.
Rate this page: