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.
We’re happy to introduce two new Jira Forge product events:
Component deleted - avi:jira:deleted:component
Issue type deleted - avi:jira:deleted:issuetype
Follow the links to read more about them.
UI modifications, the Forge module that allows apps to modify fields, now supports the cascading select field on the Global issue create view.
For more information, see the list of supported fields for Global issue create.
We have now removed the UI Kit @forge/react version 9 from the Forge platform. This UI Kit version was deprecated on Aug 28, 2024.
We recommend using the latest version of UI Kit (@forge/react10).
For more information, see our deprecation policy.
The non-public endpoint /rest/teams/1.0/teams/find will be removed as part of the changes coming to Teams. This change is necessary to streamline our API offerings and improve performance. This change will take effect 3 months from this notice 05 Mar 2025.
If you have integrations with this internal API endpoint, migrate your system to use the teamSearch GraphQL query instead.
Jira Forge now supports the group, groups, user, users, date, and date time custom fields on the new Transition view. This means that we’ve released support for all custom field types on the new Transition view, thus getting it to full parity. Note that you have to enable the view on your instance to be able to use it.
For more information about the Transition view, go to our documentation.
We’ve added the jira:issueNavigatorAction module to Forge. You can use it to create custom actions on the issue navigator view. For more details, see the Jira issue navigator action documentation.
To be able to use the new module, you must first update the Forge CLI: npm install -g @forge/cli@latest
We’ve just introduced multiple new display conditions for use with Jira Forge modules, including conditions for checking entity properties. The new arrivals also include conditions for app licenses and permissions, as well as the powerful Jira expression condition. We’re happy to say that, with this change, Forge display conditions have now reached feature parity with Connect.
See more details in the documentation: Display conditions.
We’ve introduced the jira:timeTrackingProvider Forge module. You may now register a time tracking provider and configure your UI elements to be visible based on the active provider using display conditions. See the Jira time tracking provider documentation for more details.
Additionally, we’ve introduced the avi:jira:timetracking:provider:changed Jira event which you can subscribe to using a trigger module. This event is emitted whenever the active time tracking provider changes.
As of today, version 3 of the Jira REST API has been promoted to general availability(GA). We are updating the classification to more accurately reflect the stability and production readiness of the v3 API.
The official recognition of version 3 of the Jira REST API as Generally Available (GA) provides greater clarity for developers regarding the API’s usage in production scenarios.
This announcement doesn’t affect the functionality of either the v2 or the v3 API, so there’s no action required from you.
There are currently no plans to deprecate v2; we will continue to provide general availability-level support for both the v2 and v3 APIs.
In 23 February 2025, we will enforce a hard limit on the rich text field size to a maximum of 1MB in Atlassian Document Format (ADF).
An error response will occur if the limit is exceeded while creating or updating a rich text field in:
the UI
operations via REST APIs
automation rules
issue transitions
Existing data that is already over the limit will not be affected until an attempt is made to update the data. All existing and migrating issues over the limit will be retained as is.
You may need to update your app as a result of this change. See the More details section.
An error will be returned when creating a new rich text field, or updating an existing rich text field to more than 1MB in ADF.
Example Scenarios:
An app populating a custom Connect rich text field with 1MB of ADF text will result in an error returned in the API.
An app updating the description of an issue from less than 1MB to greater or equal to 1MB ADF will result in an error returned in the API.
An automation rule that sets the description to a rich text body larger than 1MB of ADF will result in the failure of the automation rule.
A user creating a new comment with larger than 1MB of ADF will result in an error returned in the UI.
Rich text field limits | Impacted APIs | Operations will result in an error after the change | Response for exceeding ADF limit |
1MB ADF per description |
|
|
|
1MB ADF per environment | |||
1MB ADF per comment body |
| ||
1MB ADF per worklog body |
| ||
1MB ADF per rich text customfield |
| ||
1MB ADF per rich text connect field |
|
Whilst the vast majority of our rich text fields have a reasonable length, there are some texts with extreme data shapes, e.g. 24MB in an issue description due to a legacy bug. These data sizes can lead to reliability issues and incidents in unpredictable ways.
This new limit will not impact most users as 99.99% of Jira instances already have a standard 32KB wiki text limit that will continue to be applied.
No changes to your app are necessary if your workflows do not add or edit rich text fields with a size above the limit.
If your app is performing operations that would cause it to exceed limits, you need to handle the new error message appropriately.
If your app needs to create ADF content over 1MB, consider adding it as an attachment to the rich text field.
We’re happy to introduce new Jira Software Forge product events for filters:
filter created - avi:jira:created:filter
filter updated - avi:jira:updated:filter
filter deleted - avi:jira:deleted:filter
Follow the link above to read more about them.
UI modifications, the Forge module that allows apps to modify fields, now supports the cascading select field on the Issue view.
For more information, see the list of supported fields for Issue view.
We’re happy to introduce a new Jira Forge product event:
Project version deleted - avi:jira:deleted:version
Follow the link above to read the event’s documentation.
UI modifications, the Forge module that allows apps to modify fields, now supports the original estimate field on the Issue view.
For more information, see the list of supported fields for Issue view.
Rate this page: