Optics Migration from Connect to Forge

Optics is undergoing a major platform upgrade. The app is being migrated from Atlassian Connect to Atlassian Forge. The user experience stays largely the same. The main change is behind the scenes: Optics will run on Forge for hosting and execution.

Forge is Atlassian’s next-generation app platform, built for stronger security, improved reliability, and tighter integration with Jira and Confluence. It is also Atlassian’s long-term direction for Marketplace apps, and many newer platform capabilities are delivered on Forge first.

To be considered a Forge app, Optics must run fully on Forge. This means all existing modules, macros, and backend logic previously built on Connect are being rebuilt using Forge modules. Partial migration is not the target state. Once complete, Optics will be a 100% Forge-based app.

This migration improves long-term stability, compliance, and scalability. Moving Optics to Forge keeps the app aligned with Atlassian’s evolving cloud platform and enterprise requirements.

Atlassian Connect and Atlassian Forge are two different app platforms for building apps on Atlassian Cloud. While both are supported today, Forge is Atlassian’s strategic platform for the future.

Forge apps run within Atlassian’s infrastructure. Execution, permissions, and data access follow Atlassian’s platform controls rather than external hosting models. This provides stronger isolation and a more standardized approach to operating apps in Atlassian Cloud environments.

• Stronger security and clearer data access boundaries

• Improved reliability through execution within Atlassian infrastructure

• Better alignment with Atlassian’s cloud architecture and roadmap

• A foundation for faster delivery of future improvements

Throughout the migration, existing functionality is preserved wherever technically possible. However, Forge introduces different architectural constraints and capabilities compared to Connect, so some internal behavior, performance characteristics, or configuration flows may change.

The current AI-based card creation feature is not compatible with Atlassian Forge and will be removed as part of the migration. This AI solution was built on the previous platform and cannot be supported in a Forge-only environment.

A new AI implementation is planned and will be rebuilt to align with Forge and the LLM technologies supported by Atlassian. This will ensure better compatibility, security, and long-term support.

By the end of February, a new version of Optics will be released that moves most core modules from Connect to Forge. This is the first major step in the overall migration.

After updating to this version, customers will start to see the benefits of Forge in day-to-day usage. From this point onward:

• The app execution and hosting move to Atlassian’s infrastructure

• Most functionality is delivered through Forge modules

• Performance and reliability improvements become visible to users

Some features and flows will change as part of the Forge migration, and a few items need improved handling or replacement before they can move fully to Forge. During March, the focus is to finalize these topics and communicate the impact clearly, so customers know what changes, if any action is required, and the migration stays smooth.

For this reason, two modules will temporarily remain on Connect after initial relase. This allows Optics to stay stable while the required changes are completed and clearly communicated.

By the end of March:

• All remaining migration topics will be communicated to customers, including what changes and what actions are required

• The last two Connect modules will be migrated

• Optics will become a 100% Forge-based app

The following features are currently not compatible with Forge and will be temporarily unavailable as part of the migration.

The Designer macro is deprecated and is no longer supported. This macro was built a long time ago, and over time it became clear that it could not properly support modern Confluence use cases or align with the Forge platform.

Going forward, all development focus is on Dex → documentation.

Dex is the next generation of content creation in Optics. It is designed to replace what Designer was originally meant to do, but in a more structured, scalable, and user-friendly way. Dex provides:

• Ready-to-use templates for common Confluence use cases

• Better design and layout options

• Easier configuration and usage

• Presentation-ready content

• Ongoing improvements and long-term support

• Full alignment with Forge and Atlassian’s cloud platform

Optics includes the Nested Macros feature (Tabs and Panels).

Forge limitation: Atlassian Forge does not support third-party macros inside nested macro containers. This also affects Caelor macros, such as Cards, Buttons, and other Optics modules, when placed inside Tabs or Panels. While it is technically possible to build a workaround, it is a very time-consuming approach, so the focus is to monitor real usage and demand to understand how important this capability is for customers.

Because of this, the migration is handled in phases:

1. Until the end of March, Nested Macros will remain available as a Connect module to avoid breaking existing pages and use cases during the transition.

2. The Forge version of Nested Macros will be released without support for third-party macros inside nested containers.

3. To support customers who still require third-party macro nesting, the following approach will be used:

   1. A separate, private Connect app version can be provided for customers who need third-party macro support inside Tabs or Panels.

   2. This private app is not connected to the Forge app, and it remains Connect-based.

   3. It will work as long as Optics is installed and licensed.

If there are any questions about the Forge migration, feature changes, or upcoming milestones, the support team is available to help.