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 Software Cloud.
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 ability to build Forge apps that are compatible with multiple Atlassian apps is now available in Preview. This feature allows you to declare compatibility in your app’s manifest and enables your app to be installed and used across Jira, Confluence, and Compass.
For more information, see App compatibility.
The following flows are available for testing in this Preview:
Create, deploy, and install an app via the CLI
Distribute the app via a direct distribution link
View and connect/disconnect compatible Atlassian apps in Connected Apps
Add the app to Marketplace
Important considerations:
Customer release (GA) is planned for the end of January 2025.
Until GA: We recommend keeping Marketplace apps private, as customer-facing changes are not yet available (admins currently only see the required app in the consent screen when installing).
For guidance on migrating existing apps, see our migration guidelines.
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.
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
Forge platform will be undergoing maintenance in commercial production on October 12, 2025 for approximately 1 minute between 3-4am 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.
Starting Mar 31, 2026, the ability to update existing Jira or Confluence apps using a Connect descriptor on the Atlassian Marketplace will be deprecated. This change aligns with our strategic shift to the Forge platform.
Additionally, this means the following:
Atlassian Marketplace will no longer poll for Connect descriptor updates. However, apps using Connect modules that have adopted the Forge manifest can still receive updates.
Installing new Connect private apps via Connected Apps will no longer be available and private app development should move to Forge.
What this means for partners:
Partners should plan to update Connect apps on the Atlassian Marketplace by Mar 30, 2026 at the latest.
All new app development should be conducted on Forge.
See the Adopting Forge from Connect documentation to know more about how to migrate to Forge
We're introducing new App Property API endpoints to retrieve Forge App Properties in Confluence & Jira, now available in Preview.
The APIs enable developers to
GET all Forge app properties, or
GET individual app properties by key
in both Jira and Confluence, enhancing the flexibility and functionality of Forge apps.
For further details on implementing this new feature, refer to the Jira App Property API Documentation & Confluence App Property API documentation.
Following a recent incident (see details), we have temporarily paused automatic Connect to Forge migrations. Our team is actively working to enhance system robustness and prevent similar issues from occurring in the future.
Once these improvements are complete, we will re-enable and resume the migration process.
Following our prior deprecation notice, you can no longer publish a new Jira or Confluence app using a JSON Connect descriptor to the Atlassian Marketplace.
From now on, all Atlassian Marketplace apps should be built using Atlassian’s Forge platform.
Learn more about the announcement of our timelines for the end of support for Connect. Existing apps built with Connect should explore https://developer.atlassian.com/platform/adopting-forge-from-connect/.
Forge platform will be undergoing maintenance:
in FedRAMP production on September 21, 2025 between 5-6am UTC
in commercial production on September 28, 2025 between 5-6am 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 allow-popups attribute of the sandbox directive (content security policy) is now supported in Forge Custom UI and UI Kit apps when using * as your client egress configuration. This enables external content (such as those from 3rd party integrations) to open properly in new tabs instead of being blocked by browser security restrictions.
With this enhancement, external content will open in a new browser tab while keeping your Forge app running.
For more information, see the valid domain formats documentation.
The Forge https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-issue-panel/ module now supports options to show or hide a panel in all work items throughout a project.
These options dynamically appear in the panel’s action menu, depending on whether the panel is hidden or displayed in all work items. The action menu will show the Show for all work items option if the panel is hidden on all or some work items. Selecting this option will replace it with the Hide from all work items option. Both options will show/hide the panel on all work items throughout the project.
You can now name transitions that allow issues to move into a status from anywhere in the workflow.
Create Transition Modal:
Enable users to name ‘from any status’ transitions during creation.
Transition Side Panel:
Allow users to update ‘from any status’ transition names.
Status Side Panel:
Display the transition name.
Edit Status Modal:
Provide an option for users to retain the existing transition name or update it to match the new status name.
Add a transition preview card for this type of transition.
Rate this page: