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.
Forge Automation Actions are now available as an Early Access Program (EAP) feature for Forge. This feature allows developers to extend the Atlassian Automation Platform and add new Forge-based actions to the Automation Platform.
To sign up for this EAP, use the request form. As per the Atlassian Developer Terms, EAPs are offered to selected developers for testing and feedback purposes. APIs and features under EAP are considered “Early Access Materials” and are unsupported, subject to change without notice, and can’t be used in production environments.
For more information about this new capability, refer to the Forge documentation for the Forge Automation Actions.
To enhance the security and consistency of comment visibility in Jira, we have implemented a restriction on changing the visibility of child comments. This update ensures that child comments inherit the visibility settings of their parent comments, promoting consistency across comment threads to ensure the flow of communication is maintained. This will not impact modifying the visibility of the parent comment.
Concerned REST API: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-comments/#api-rest-api-3-issue-issueidorkey-comment-id-put
Details:
Visibility Inheritance: Child comments will automatically inherit the visibility settings of their parent comments. This means that any changes to the visibility of a parent comment will be reflected in all its child comments.
API Update: The REST API for updating comments will no longer allow changes to the visibility of child comments. Attempting to update a child comment's visibility will result in a 400 (Bad Request) error.
Impact:
API Usage: Customers using the API to modify comment visibility should be aware of this change and adjust their usage accordingly. This will not impact modifying the visibility of the parent comment.
Examples:
Case 1: If a parent comment is visible and a user attempts to restrict a child comment to another visibility using the API, the request will fail with a 400 error.
Case 2: If a parent comment's visibility is changed to restrict access, all child comments will automatically inherit this restriction.
We appreciate your understanding and cooperation as we work to improve the security and functionality of Jira comments.
The previous announcement for Project/Fields Association Improvements for team-managed projects has been updated to clarify that all fields are affected by the change and not just user-created custom fields.
Re-read the announcement by visiting https://developer.atlassian.com/changelog/#CHANGE-2278
Internationalization (i18n) for Forge apps is now generally available. This allows you to add translation support to your app so that it can adapt based on a user’s language and locale.
In addition to the Confluence and Jira modules that were supported during the EAP, internationalization support can now also be added to Bitbucket, Compass, and Jira Service Management modules, as well as Forge resolvers.
For more information, see Internationalization.
Introduced the new property nav.isNewNavigation in the context object returned by the getContext method in the Jira Connect JavaScript API context module. This field allows Connect apps to determine if their iframe is displayed on a site using the old or new navigation.
1
2
3
AP.context.getContext(function (context) {
const { isNewNavigation } = context.nav;
})After our announcement in June 2024, we’ve now successfully completed the migration of Forms (previously ProForma) data from Jira entity properties. This will now enable us to build new functionality and increase performance and reliability of Forms.
Starting May 1 2025, we’ll begin removing access to historical Forms data available via Issue properties routes and Project properties routes in order for us to complete post-migration work.
You will still have full access to your Forms data though the Forms REST API.
If you’re currently using Jira Issue entity property smart values to access Forms data in Automation, we will continue to support this however we encourage you to consider moving any Automation to our new Forms smart values.
Forge Remote Data Residency realm migrations is now available in GA. This release provides apps with the ability to support customer-initiated migrations between data residency regions.
Please review the documentation to learn more about how to support realm migrations in your app.
We have added support for the loopedTransitionContainerLayout in workflows across the following APIs:
This property allows you to control the positioning of the global looped transition container within a workflow.
For instance, To display the global looped transition container roughly above an ‘in progress’ status:
First, read the workflow using the get workflows API to obtain the workflow and find the in-progress status position:
1
2
3
4
"layout": {
"x": 901.8984375,
"y": 114.98200988769531
}Then set the position of the looped container in the workflow relative to that position using the update workflows API.
1
2
3
4
"loopedTransitionContainerLayout": {
"x": 901.8984375,
"y": -151.5851593017578
},This will result in the loopedTransitionContainer being displayed above the in-progress status as shown below:
If not supplied the loopedTransitionContainer will be cleared and we will automatically position it as is done today.
The extension context now includes navigation details that indicate whether a customer is viewing the new or old navigation system, represented by the structure { "jira": { "isNewNavigation": boolean } }, for all Jira Forge apps. This allows developers to customize their Jira Forge apps according to the type of navigation the customer is using.
From Nov 1, 2025
The following projectTemplateKey values will cease to be valid for the Jira Project Create API
com.atlassian.servicedesk:simplified-blank-project-it
com.atlassian.servicedesk:simplified-blank-project-business
com.atlassian.servicedesk:simplified-general-service-desk-it
com.atlassian.servicedesk:simplified-general-service-desk-business
com.atlassian.servicedesk:next-gen-general-it-service-desk
com.atlassian.servicedesk:next-gen-general-business-service-desk
From Apr 1, 2025 , you should now use one of the following project template keys instead:
com.atlassian.servicedesk:company-managed-blank-service-project
com.atlassian.servicedesk:company-managed-general-service-project
com.atlassian.servicedesk:team-managed-general-service-project
The follow table outlines the recommended replacements
Deprecated Template | New Template |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
Rollout: progressive rollout by tenant COMPLETED
Following our earlier deprecation notice, the changelog item for the parent field (IssueParentAssociation) in Team managed projects will change to have attributes fromString and toString return issue keys instead of issue ids.
The issue id remains available in the from and to attributes.
We will not be issuing any new waivers for apps that need to request or store Atlassian user API tokens. This decision is part of our ongoing commitment to enhancing security and protecting customer trust.
Forge Apps that have already been granted waivers must ensure a lack of alternative solutions within Forge. They can continue to operate, but no additional waivers will be granted for new modules or new functionality within the same app.
Connect apps that have been granted waivers and any existing Connect app requesting or storing Atlassian user API tokens are required to migrate to Forge, with tokens stored in Forge encrypted storage.
For more details, read our FAQ
Rollout: progressive rollout by tenant
We are adding a Public access option to the forms available in Jira business and software projects. Any user, including those without a Jira license, will be able to make a submission through a public form.
Only users with project admin permissions will be able to create a public form and these will be available for all licence editions and both team-managed and company-managed projects. In addition, Jira admins will be able to disable public forms in their site. There is one setting for team-managed projects and one for company-managed.
An unlicensed user will be able to make a submission through a public form, but to view and collaborate on the work item created from their submission, they will need a Jira license.
There are no specific APIs or UI extension points currently available in Connect or Forge for forms. But we would love to hear your feedback and ideas on how we could provide value for existing or new apps in the future.
We have updated our UI Kit components, Text and Heading to make them more flexible:
Text
Now supports align, as, color, maxLines, size and weight properties.
For more information, see Text component documentation.
Heading
You can now control how the Heading component appears by setting a value for size, while the as prop controls the HTML element's rendering.
For more information, see Heading component documentation.
In the latest version of @forge/react, we're adding a new disableSubmitOnBlur property to the UI Kit Jira component, CustomFieldEdit. The property can be used to disable the submission of the field value on blur events.
For more information on this component, see the component documentation.
To update your UI kit app to the latest version, run the following command in your project directory:
npm install --save @forge/react@latest
Rate this page: