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 are changing the way we measure rate limits across Jira and Confluence Cloud for all free and paid apps. A phased enforcement of the new rate limits will begin on February 2nd, 2026.
When the phased enforcement begins, API requests then start consuming points based on the work they perform, such as the data (objects) returned or operations triggered. Each request starts at a base point of 1 point, with additional points for each object involved.
We’re also introducing two types of app-level quotas (tiers) that apply consistently across the Atlassian platform for all apps.
It’s important to note that the vast majority of free and paid apps do not require any changes and are already operating within these limits. We’ve also reviewed usage and upgraded eligible apps to a higher tier where appropriate.
If your app requires additional capacity in the future, rest assured we will provide clear pathways to request for this. For more information, please refer to the following documentation:
Here’s how the points-based limiting works.
Points-based measurement | API requests consume points based on the work they perform, such as the data (objects) returned or operations triggered. Each request starts at a base point of 1 point, with additional points for each object involved. |
|---|---|
Two-tier quota system | Apps start in Tier 1 - Global Pool, with a shared hourly quota across all tenants. Apps with consistently high or concentrated usage may qualify for Tier-2 Per‑Tenant Pool, which provides dedicated hourly quotas per tenant. |
Points-based costs | Different objects have different point values:
|
Hourly quotas by edition | Quotas reset at the top of each UTC hour. Per-tenant pool quotas vary by customer edition and number of users. |
Here are the benefits for you:
Fairer limits, heavy operations use more quota than simple ones.
This provides more predictable API usage planning and scaling.
This gives you better visibility through detailed rate limit headers.
The vast majority of free and paid apps already operating well within the new limits.
Some updates you need to know:
Updates to the RateLimit-Reason header with new reasons:
jira-quota-global-based, which refers to the Global pool limits being breached in Jira
jira-quota-tenant-based, which refers to the Per Tenant pool limits being breached in Jira
confluence-quota-global-based, which refers to the Global pool limits being breached in Confluence
confluence-quota-tenant-based, which refers to the Per Tenant pool limits being breached in Confluence
Updates to the developer documentation regarding rate limit quotas for different tiers in both Jira and Confluence
Planned updates to the developer console to show which tier your app belongs to ahead of the enforcement
Currently, the new workflow editor is the default editing experience in Jira and is being used by the majority of customers.
Starting 26th June 2026, we will begin removing the old workflow editor for customers, which means workflows will only be editable in the new workflow editor. We ask you to please help your customers in this transition by ensuring that any workflow-related apps will work effectively with the new workflow editor.
If you encounter any issues with how your apps behave in the new workflow editor, please raise a support ticket.
Some features to be aware of to improve app experiences in the new editor:
Dynamic configuration descriptions (Forge/Connect)
Make sure to provide a unique description for configured rules.
Additional context (Forge/Connect)
Determine whether the rule is loaded in the new or old workflow editor.
Default workflow editor for user (API)
Determine whether a user has a preference set for the new or old editor.
Deep linking to statuses and transitions
Link to the new workflow editor and provide an ID with either the selectedStatus or selectedTransition query params to pre-select a status or transition.
Following the Preview release, the Forge Automation Actions is now generally available. The Automation action module allows you to extend the Automation Platform and add new Forge-based actions to your app. With this release Forge Actions can now output smart values, enabling seamless data flow and dynamic automation.
For more information, see the Forge Automation Action module documentation.
Previously, the behavior of labels in Jira was inconsistent - some experiences treated labels as case-sensitive, while others did not. To provide a more predictable and unified experience, we are making labels case-insensitive in all grouped aggregations. This means that labels differing only by letter case (for example, "Bug" and "bug") will now be treated as the same label when aggregating data.
This update will be most noticeable on Jira dashboards and in Jira Work Management (JWM). No action is required from developers.
Forge platform will be undergoing maintenance in commercial production on November 23, 2025 for approximately 1 minute between 5:30-6:30am UTC
During this interval, below capabilities will not be available intermittently:
Create/update/delete apps
Deploy apps
Install/uninstall/upgrade apps
App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.
The sidebar will now span the full height of your Atlassian app, making it easier to find and interact with. Starting late November 2025, this update will roll out to all customers who haven’t customized the look and feel of their sites. This change won’t affect the width and height of your Forge and Connect apps.
Along with this, we’re introducing a few improvements to sidebar interactions:
Double-click to collapse: When expanded, double-click the button to quickly collapse the sidebar.
Global shortcut: Use Ctrl + [ to expand or collapse the sidebar at any time.
Helpful tooltips: Tooltips will appear to guide you through the interaction.
For sites with customized look and feel, the full-height sidebar can disrupt intentional design choices, such as:
Custom logos and titles
Favicons
Navigation colors
Dark and light mode settings
Because of this, the sites with customized look and feel won’t receive the update just yet.
For the sites without customized look and feel, we’re opening up the opportunity on Nov 21, 2025 to let you use this feature early and test it with your apps. If you’re interested, please sign up here with your site details.
As part of our new design language, the refreshed colors and components in the Atlassian Design System (that first launched in products at Team '25) are now officially in GA. Also included is a further tweak to accent token colors in hover/pressed states to improve accessibility.
What you need to do if you are using Forge Custom UI or Atlassian Connect:
Bump @atlaskit/tokens + relevant component packages to the latest version to align your app's look and feel with Atlassian apps.
What you need to do if you are using Forge UI Kit or Forge UI Kit 2:
Nothing! You should have the newest components by default.
Visual changes to Atlassian components and tokens:
New base color tokens: We've introduced new color stops across our base color ramps, namely 250 and 850, to support better hover/pressed state contrast and improve WCAG AA accessibility.
The GET methods of the Key-Value Store and Custom Entity Store SDKs can now return optional metadata fields, namely:
createdAt
updatedAt
You can now provide dynamic descriptions for the configuration of Forge workflow conditions, validators and post functions. These descriptions will appear on the overview card for configured rules in the new workflow editor and help admins locate previously configured rules.
Use the configurationDescription property and provide a Jira expression, which can reference the config context variable to describe the current configuration of the rule.
You can now enable your Forge workflow conditions, validators and post functions in team-managed workflows. Use the projectTypes property to configure whether your rule should be enabled for company-managed projects, team-managed projects, or both.
You can now provide dynamic descriptions for the configuration of Connect workflow conditions, validators and post functions. These descriptions will appear on the overview card for configured rules in the new workflow editor and help admins locate previously configured rules.
Use the configurationDescription property and provide a Jira expression, which can reference the config context variable to describe the current configuration of the rule.
The following UI Kit Editor components are now available through Forge’s Early Access Program (EAP). To join, please complete this sign-up form.
These components are available in Confluence and Jira modules.
When defining resolvers, the front-end code can share the types with the backend so the invocation interface is type-safe. This helps catch potential errors during compilation.
Forge Automation Actions is now available in Preview. This feature allows you to extend the Automation Platform and add new Forge-based actions to your app. During Preview, the Automation Actions in your app can be used in production environments.
For more information, see the Forge Automation Action documentation and share your feedback to help us improve
As of Oct 9, 2025, we’ll be moving the location of the configuration for JSM approvals in company-managed projects from status properties to a new approvalConfiguration property on the status. The following endpoints will be affected:
Refer to CHANGE-1656 for more details.
Rate this page: