Last updated Feb 27, 2024

Changelog

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.

27 February 2024

Announcement Realm persistence is coming soon for Connect data residency

In the upcoming quarter we plan to update our Connect data residency service to support realm persistence.

Realm persistence allows partners to save time and avoid negative customer experience by helping to ensure that customer app pinning does not move between realms upon reinstallation. With realm persistence, app pinning will only move when the app is reinstalled outside of a defined duration or when otherwise requested to move by the customer through the realm migration service.

If you are waiting to implement data residency for your Connect app due to realm persistence concerns. Keep an eye out here in the change log for updates in the coming weeks.

More details

Today, apps built on Connect can support both realm pinning and realm migration to help customers keep their data in a region they trust.

Read more about data residency for Connect apps →

26 February 2024

Removed Partial removal of lenient URL path processing for OAuth 2.0 requests

Rollout: progressive roll-out by request. in progress

The extended deprecation period for Lenient URL path processing for OAuth 2.0 requests has now expired. This change will be rolled out progressively over the coming week.

23 February 2024

Added Sprint name and goal can now be updated for closed sprints

Sprint names and goals can be updated for closed sprints using both the full and partial sprint update endpoints. Any changes to other sprint fields are ignored.

22 February 2024

Announcement App access rule status for each API now included in Jira REST API reference pages

A Data Security Policy section for each API now indicates whether the API is exempt from app access rules or not. You can find this in the REST API references pages, and the downloadable OpenAPI specifications associated with them, for:

You can use this to prepare your apps prior to General Availability of the app access rule functionality. It is scheduled for customer release by the end of Q1, 2024 (31 March).

More details

This information augments the App access rule coverage summary for Jira Cloud and the detailed App Access for Jira Cloud APIs documents for administrators published previously.

We recommend that you:

  • Carefully review the app access rule details for the APIs your app uses

  • Consider how you want your app to behave when APIs that are subject to being blocked return no data, or fewer rows of data, due to an app access rule.

For more information on how app access rules may impact app functionality and how to manage the customer experience, see the https://developer.atlassian.com/cloud/jira/platform/data-security-policy-developer-guide/ .

Announcement Data security policy events documentation now published

To prepare your apps for the upcoming General Availability of app access rule functionality, we’ve published documentation on new data security policy events. Customer release is scheduled for the end of Q1 of the calendar year 2024.

The new events will be available for early access by developers in late February, 2024. We’ve published this documentation in advanced so you can start preparing your apps to receive the event notifications when appropriate.

More details

We have updated the following guides with information about the new data security policy events your app can subscribe to:

Additionally, a new https://developer.atlassian.com/platform/forge/events-reference/data-security-policy-events/ reference page has been added for Forge app developers.

21 February 2024

Added Adopting Forge from Connect (preview)

We’re pleased to announce the preview availability of adopting Forge from Connect.

Existing Connect apps now have a simpler, automated and incremental pathway to adopt Forge capabilities. This release includes:

  • Automated tooling to support the conversion from Connect to Forge

  • Support for immediate version updates of Forge apps containing connectModules

  • Increased compatibility for the types of connectModules that can be declared within a Forge manifest

  • Support for Forge Remote Compute (preview) in the Atlassian Connect Express (ACE) and Connect Spring Boot (ACSB) frameworks.

16 February 2024

Deprecation Notice Epic issues in team-managed projects can soon have parent issues from other projects

This change announced in November will take effect from 27th February 2024 with a progressive rollout. It only applies to Premium and Enterprise instances of Jira Software Cloud.

To further improve Plans for Jira Software Cloud, team-managed projects will no longer restrict parent association for hierarchies above epic to the same project. The restriction on lower hierarchy levels (epic to stories and stories to subtasks) remains unchanged.

More details

This is a behavioral change on APIs that write and read parent issue associations. As a result, parent issues of epics in team-managed projects can now be from other projects.

When we roll out this change, it will then become possible to set the parent issue of an epic in a team-manager project to be an initiative issue of a company-managed project. See the below diagram for more details.

6 February 2024

Announcement App access rule under data security policies: early access for Jira customers and partners live this week

This week, select customers will be given early access to the app access rule for Jira Cloud. Customers will be asked to test the functionality, and warned that app functionality will be impacted when apps are blocked from accessing projects.

Marketplace Partners in the app access rule EAP have had access to this feature in Confluence since November 2023. Early access participants will now be given access to the feature in Jira and to the Jira app access rule API. This will allow you to prepare your apps for any potential end user impacts when the app is blocked by an app access rule.

More details

Data security policies help customers keep their organization’s data secure by letting them govern how users, apps, and people outside of their organization can interact with content such as Confluence pages and Jira issues.

The new app access rule under data security policies allows customers to restrict access for all apps to the Confluence spaces or Jira projects under a given policy. This should make it easier for customers with more strict data privacy concerns to install your apps while maintaining control over access to certain content.

If you’d like to participate in the developer EAP for this feature, which gives you access to the app access rule and new app access rule API to test, sign up here.

5 February 2024

Deprecation Notice Default realm migration downtime will be reduced for Connect apps in August 2024

After observing several successful realm migrations for Connect apps, we have determined that the default downtime window of 24 hours is too long for most apps.

To improve customer experience and better reflect the true downtime needed for most Connect apps to migrate data, we will be reducing the default downtime window to 2 or fewer hours starting early August, 2024 and enabling partners to declare their own downtime.

Understanding that some apps may require more than a few hours to complete data residency migrations, the ability to define a maxMigrationDuration for data residency realm migrations will be made available prior to the implementation of this change. This will enable apps to declare up to 24 hours of downtime, where they have large amounts of data or complex data storage. If you fail to update your downtime window and a migration takes longer than the default, your migration may fail.

We will provide instructions on how to update your app descriptor with a custom downtime window in the coming months in preparation for the change. Keep an eye out here in the change log for more information in late March/early April.

More details

Realm migration allows customers to request app data be moved to the same region as the host product via the Data Residency tab in admin.atlassian.com.

Today, apps built on Connect can support both realm pinning and realm migration to help customers keep their data in a region they trust.

Read more about data residency for Connect apps →

2 February 2024

Added Account-level permission grants for Forge and 3LO Jira apps

Starting this week, customers will be able to grant permission to Forge and 3LO Jira apps at the account level. This means that after granting permissions for their account, they no longer need to give an app permission when using the app on a new site where it has previously been installed and given permissions.

This will prevent scenarios where app functionality has been impacted in the past when the installation and app permission grant process have been out of sync. In this way, we expect this change to smooth the customer app installation experience.

More details

Customer impacts will be limited to slightly different arrangement of the access consent screen. Also, after consenting, customers will not need to re-consent each time they use an app in a site where it is already installed.

New 3LO apps consent screen:

 

To read more about 3LO apps and consent, click here.

New Forge apps consent screen:

18 January 2024

Announcement Coming soon: developer early access to app access rule Jira API

At the end of January 2024, partners in the app access rule EAP will be given access to the app access rule to test in a Jira environment, as well as the Jira app access rule API for testing.

If you have any concerns about how your app may appear or behave in Jira environments where it is blocked, we recommend joining the EAP to test out the feature. The EAP will also give you an opportunity to make any changes to your app to prepare for the new feature.

If you’d like to participate in the developer EAP for this feature, which gives you access to the app access rule and new app access rule API for testing, sign up here.

More details

Data security policies help customers keep their organization’s data secure by letting them govern how users, apps, and people outside of their organization can interact with content such as Confluence pages and Jira issues.

The new app access rule under data security policies allows customers to restrict access for all apps to the Confluence spaces or Jira projects under a given policy. In this way, customers can benefit from apps while still limiting 3rd-party access to certain content in select spaces.

Announcement New region available for Connect data residency

Atlassian’s data residency has expanded and Switzerland (CH) is now available for partners to support for Connect apps.

Find out more about data residency and how to support it in your app.

12 January 2024

Announcement Five new regions available for Connect data residency

Atlassian’s data residency has expanded and these new regions are available for partners to support for Connect apps:

  • India (IN)

  • South Korea (KR)

  • Brazil (BR)

  • Japan (JP)

  • UK (GB)

Find out more about data residency and how to support it in your app.

2 January 2024

Announcement Ticketing has begun for new Forge scanners

In December 2023 we added new Forge scanners to our suite of scanners that continuously scan Forge apps on the Marketplace. We are now ticketing apps who are found to be missing requirements based on these new scanners.

Please read the blog post on partner portal for a full announcement here.

More details

These scanners have been available to Marketplace Partners since early December, and we are now ticketing cloud apps. We are committed to working collaboratively with you and continue to improve the security of our cloud apps and foster trust with our customers.

15 December 2023

Announcement Clarify language around component API response change

We recently rolled out a feature allowing users to use Compass components in their projects, instead of the usual Jira components. To learn more about this feature check out https://community.atlassian.com/t5/Compass-articles/Compass-Components-in-Jira-Software-are-coming/ba-p/2552172.

Turning this feature on also changes the way some of the existing APIs function and their responses. The impacted APIs are the Project components API, issue creation and editing.

More details

Compass Components in Jira

This feature allows users to leverage Compass components, rather than Project components in issues' components field.

In order to determine whether a specific project is using Compass components or not, API users can leverage the existing project properties API in order to check the jira.global.components property. For projects where this feature is active, that value will be true.

Doing so changes the behavior or a number of APIs around components, issue creation and editing.

Project components API

In both the v2 and v3 API, turning Compass components on will prevent API users from creating, updating or deleting project components for that project.

Issues API

In both the v2 and v3 API, turning Compass component on will prevent users from creating issues with project components attached, or adding project components to existing issues. Removing project components from existing issues is still allowed.

Rate this page: