Changelog

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.

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.

1. Create Transition Modal:

   • Enable users to name ‘from any status’ transitions during creation.

2. Transition Side Panel:

   • Allow users to update ‘from any status’ transition names.

3. Status Side Panel:

   • Display the transition name.

4. 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.

We are announcing support for the following Forge Jira Software provider modules. More information can be found in our documentation: https://developer.atlassian.com/platform/forge/manifest-reference/modules/index-jsw/

• devops:developmentInfoProvider

• devops:featureFlagInfoProvider

• devops:deploymentInfoProvider

• devops:buildInfoProvider

• devops:remoteLinkInfoProvider

We will be removing the ability to use two unlisted board endpoints on Jul 22, 2025:

• /rest/greenhopper/1.0/xboard/work/allData

• /rest/greenhopper/1.0/xboard/work

As an alternative, consider the following public API options:

• https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-boardid-issue-get for board issues

• https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-boardid-sprint-get for board sprints

• https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-group-board for an extensive list of public board endpoints

The following UI Kit components are now generally available:

• https://developer.atlassian.com/platform/forge/ui-kit/components/adf-renderer/

• https://developer.atlassian.com/platform/forge/ui-kit/components/calendar/

• https://developer.atlassian.com/platform/forge/ui-kit/components/checkbox-group/

• https://developer.atlassian.com/platform/forge/ui-kit/components/empty-state/

• https://developer.atlassian.com/platform/forge/ui-kit/components/inline-edit/

• https://developer.atlassian.com/platform/forge/ui-kit/components/list/

• https://developer.atlassian.com/platform/forge/ui-kit/components/popup/

• https://developer.atlassian.com/platform/forge/ui-kit/components/time-picker/

No code changes are required. These components will now follow the 6 month deprecation period if any breaking changes were to be made.

As part of the Atlassian visual refresh updates, we updated the UI Kit Icon component. Some glyphs get a new look, and many more glyphs have been added. There are also a number of deprecations, as detailed below.

Forge Remotes are now available in the Atlassian Government Cloud. Please refer to the AGC documentation for details on supporting Forge Remotes within your AGC Forge app.

We’re introducing the ability for apps to publish events, allowing for enhanced interoperability between apps. This feature enables apps to subscribe to events using the existing https://developer.atlassian.com/platform/forge/manifest-reference/modules/trigger/ module, opening up new possibilities for app interactions.

We have enhanced Bulk Move API to allow users to move both parent and child work items/issues in a single request, as well as move multiple work items/issues of different types in the same request.

We have published a new migration guide to assist you in transitioning your Forge custom fields to use the isInline property.

The guide includes two practical examples:

• Migrating a Forge custom field to render inline

• Migrating a Forge custom field to render in a modal

For more details, please refer to https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/#inline-edit-migration-guide