We are happy to announce we have added support for macro autoconvert to UI Kit. This allows your app to automatically insert a macro into the editor when a user pastes a recognized URL.

For more details, please see the Macro documentation.

Connect to Forge now supports the migration of the global and permission modules. For more information, see: https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-jira-global-project-permissions/

Today we published Announcing Connect End of Support: Timeline and Next Steps, following up on our earlier blog post Taking the Ecosystem Forward: An Update on the Future of Connect.

This announcement is intended for developers of Connect apps, including partners and customers with custom apps. It provides a detailed view of the phases and timing for the end of support of Connect.

Atlassian is working towards FedRAMP Moderate compliance for our new offering, Atlassian Government Cloud (AGC), with an Authority to Operate (ATO) expected in 2025.

About AGC:
AGC will enable many of our Data Center customers, including U.S. state and federal agencies and private sector clients, to transition to the cloud. Marketplace apps are crucial for our customers' workflows, and we want to ensure they remain available in AGC. Your involvement is essential as your apps are key for our prospect customers.

Benefits of participation include:

• Announcement of AGC-compatible apps during theFedRAMP Moderate session at Team 25.

• Co-marketing efforts for AGC-compatible apps during pre- and post-launch discussions.

• Future tools for custom pricing of AGC apps, available in the second half of CY2025.

Call to action:

Follow these Pilot Program Steps:

To make your app(s) AGC-compatible by June 1st, 2025, follow these steps:

1. Register your app on Forge: [Forge Registration Guide](https://developer.atlassian.com/platform/framework/agc/guides/adopt-forge-from-connect-on-agc/ )

2. Request a development instance: [Access AGC](https://developer.atlassian.com/platform/framework/agc/guides/get-access-to-agc/ )

3. Complete the remaining steps for compatibility: [Build AGC-compatible Apps Guide](https://developer.atlassian.com/platform/framework/agc/guides/build-agc-compatible-forge-apps/ )

Please note, apps made AGC-compatible after April 1st, 2025, will not be announced at TEAM 25. We kindly ask you to confirm your participation in the program.

Please leave any questions you may have as a comment on this page.

FAQ:

Do I need to convert my entire app to Forge?

• To achieve AGC compatibility, you don’t need to convert all modules to Forge. Using Connect-on-Forge is sufficient, and you can include Connect modules in your app.

I have a Forge Remote app, what should I do?

• Please inform us if you have a Forge Remote app, as it is currently not supported. We are collaborating with the team responsible for Forge Remote to introduce this capability, which is expected to be available around Q2 of the calendar year 2025.

Can my app still be AGC compatible if it includes data egress?

• Yes. You should also be able to use external static resources and allow your app to egress data (however, federal customers will still evaluate the app's security, focusing on the types of data it transmits.)

Forge Remote Data Residency realm migrations is now available in Preview. This release provides apps with the ability to support customer-initiated migrations between data residency regions.

Please review the documentation to learn more about how to support realm migrations in your app.

Forge platform will be undergoing maintenance on March 02, 2025 between 00:30 AM to 03:30 AM. During this interval, below capabilities will not be available intermittently:

• Create/update/delete apps

• Deploy apps

• Install/uninstall/upgrade apps

• View existing installations

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.