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.
The extension context provides navigation details indicating whether a customer is viewing the new or old navigation with { "jira": { "isNewNavigation": boolean } } for all Jira Forge apps. This enables developers to tailor their Jira forge app based on the customer's navigation type.
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 IN PROGRESS
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
The Jira workflow validator function has been enhanced to provide additional details about fields that have been modified during a work item transition.
To see list of all supported field types, please refer to the documentation: Jira Workflow Validator.
Connect to Forge now supports the migration of the global and permission modules. For more information, see: https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-jira-global-project-permissions/
After the beta phase of Atlassian’s new navigation, we’re thrilled to announce its General Availability (GA) for Jira, Jira Service Management, Jira Product Discovery, Confluence, and Atlassian Home. In this article, you’ll find key details about what’s changing with the new navigation, Jira and Jira Service Management apps, as well as when those changes will go live.
Starting Sep 17, 2025, the ability to publish a new Jira or Confluence app using a JSON Connect descriptor to the Atlassian Marketplace will be deprecated. This change is part of our strategic shift to the Forge platform that enables developers to leverage enhanced capabilities such as Forge Storage.
Partners should plan to list any Connect apps currently under development on the Atlassian Marketplace by Sep 16, 2025, and should undertake all new app development on Forge.
Documentation on adopting Forge from Connect, capabilities equivalences between Forge and Connect, and other details about the transition from Connect to Forge for Jira and Confluence apps are available on the Adopting Forge from Connect content site.
Today we published Announcing Connect End of Support: Timeline and Next Steps, following up on our earlier blog post Taking the Ecosystem Forward: An Update on the Future of Connect.
This announcement is intended for developers of Connect apps, including partners and customers with custom apps. It provides a detailed view of the phases and timing for the end of support of Connect.
We no longer support creation of Epic or Sub-task issue links with the create issue link REST API. This change was being made to streamline the API and improve performance.
This change has now taken effect following the published deprecation period.
We no longer support creation of Epic link or Sub-task issue links with the create issue link REST API.
Developers should use the parent field in the Issue API to create hierarchy relationships between issues.
API Reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-links/#api-rest-api-3-issuelink-post
Parent field Reference: https://community.atlassian.com/t5/Jira-articles/Introducing-the-new-Parent-field-in-company-managed-projects/ba-p/2377758
Affecting the create issue link API
Stop specifying an Epic or Sub-task link type to the API. Epic or Sub-task link type is specified by setting type.name="Epic-Story Link",type.name="jira_subtask_link"or type.id="{linkTypeId}"where linkTypeIdis the id of the Epic or Sub-task link type.
This deprecation is complete. Requests that specify these fields will return a HTTP 400 bad request instead of the current HTTP 201 created response.
Note: All other link types will continue to work as-is.
Example payload that will become invalid
1{
2 "inwardIssue": {
3 "key": "HSP-1"
4 },
5 "outwardIssue": {
6 "key": "MKY-1"
7 },
8 "type": {
9 "name": "Epic Link"
10 }
11};
Instead, provide the parent field to the Issue API (https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-group-issues) for issues of all types to create a hierarchical relationship between issues. This is described in the existing notice here: https://community.developer.atlassian.com/t/deprecation-of-the-epic-link-parent-link-and-other-related-fields-in-rest-apis-and-webhooks/54048
An example new payload would be:
1PUT /rest/api/3/issue/10054
2"fields": {
3 ...
4 "parent": {
5 "id": "10055"
6 }
7 ...
8}
In the latest version of @forge/react, we're adding a new disableSubmitOnEnter property to the UI Kit Jira component, CustomFieldEdit. The property can be used to disable the submission of the field value when the “Enter” key is pressed.
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
On February 18th, we announced that we will begin enforcing REST API (Quota and Burst based) rate limits for all free Jira and Confluence apps on or after August 18, 2025 and that we have added additional headers to provide further transparency.
To ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:
Beta-Retry-After
X-Beta-RateLimit-NearLimit
X-Beta-RateLimit-Reason
X-Beta-RateLimit-Reset
However, if you do receive headers without beta-, be advised that you are facing rate limits.
Learn more about the new limits and headers for Jira here and Confluence here.
Rate this page: