Big news... Checklists for Jira Enterprise is moving to Forge, Atlassian’s newest cloud development platform. The rollout will happen gradually, with customer flexibility on when to upgrade, careful testing, and no expected impact to your checklist data or site settings.

Checklists for Jira Enterprise is entering its next chapter.

We’re updating the app to Forge, Atlassian’s modern platform for building cloud apps. This is an important step for the product and for customers who want a future-ready app that continues to align with Atlassian’s platform direction, security model, and long-term cloud ecosystem.

The move will be introduced as a major version upgrade, which means customers can choose when to upgrade based on their own timelines and change management processes.

What’s changing

Over the coming weeks, we’ll gradually roll out the Forge-based version of Checklists for Jira Enterprise after careful testing.

• Gradual rollout: changes will be introduced progressively rather than all at once.
• Major version upgrade: customers will be able to upgrade when it best fits their plans.
• Data remains intact: your checklist data and site settings are expected to remain unaffected.
• Security and privacy practices remain in place: the app will continue to follow the same security and privacy standards customers rely on today.
  ‍

Support commitment: while we’re doing our best to ensure a smooth transition, some minor functionality or UI fixes may follow shortly after rollout. If you run into any regression issues, contact our support team and we’ll prioritize them.

Why this matters

Moving to Forge helps position Checklists for Jira Enterprise for the future of Atlassian Cloud. It gives the app a stronger foundation for ongoing compatibility, platform alignment, and future initiatives.

For customers, the goal is simple: keep the experience reliable today while making the app better prepared for tomorrow.

What to expect during rollout

We want this transition to be predictable and low-risk. Here’s the practical version of what customers should expect:

• You will not be forced into an immediate change on a fixed day.
• The upgrade will be available as a major version, so you can adopt it on your schedule.
• The rollout is planned to complete by the end of June, after which Checklists for Jira Enterprise will be fully running on Forge with Remotes.
• Any issues discovered during rollout will be handled with urgency, especially if they affect existing behaviour.

‍

Important migration guidance

If you’re planning a migration, timing matters.

Avoid migration activity during this window: if you are planning data migrations from Data Center or changing Data Residency location, we recommend avoiding the period from June 23 to July 7, 2026.

Where possible, schedule both test and production migrations before or after that window.

If you are preparing for a production migration, please let our support team know in advance. We can arrange for someone to be on standby, which helps reduce risk and speed up response time if anything unexpected comes up.

Changes from previous versions

Most of the app experience will remain familiar, but there are a few changes worth noting.

1. Mobile view is being deprecated

Forge does not currently support third-party apps inside the Jira mobile app, so the native mobile app view for Checklists for Jira Enterprise will no longer be supported.

The good news is that you can still use the web view on mobile devices when needed.

2. Checklist panel visibility may behave differently

In some cases, Jira may hide the checklist panel when a checklist was added automatically, such as through automation or default checklists.

If you want the checklist panel to remain visible for everyone in a space, space admins can pin it using the button above the checklist panel.

We also plan to introduce a global management option for this in the future, making visibility controls easier to manage at scale.

3. Minor UI improvements

You may notice some small interface updates as part of the move. These are intended to improve consistency and fit the Forge-based experience, while keeping the app intuitive for existing users.

What stays the same

• Your existing checklist data should remain unaffected.
• Your site settings should remain unaffected.
• The app will continue to follow the same security and privacy practices as before.
• The product will continue to be supported throughout the transition.
  ‍

The core message: this is a platform modernization effort, not a disruptive reinvention of the product.

Looking ahead

This Forge migration also lays groundwork for what comes next.

• Checklists for Jira Enterprise will be better positioned for future platform initiatives, including preparation for Runs on Atlassian.
• Checklists for Jira Free is also planned for a gradual migration to Forge.
  ‍

Platform transitions can raise questions, especially in enterprise environments. Our approach here is to keep the rollout gradual, give customers control over upgrade timing, and stay closely available during the transition.

We’re excited about this move because it helps ensure Checklists for Jira Enterprise stays aligned with Atlassian’s platform future while continuing to deliver the dependable checklist experience teams already use every day.

If you have questions about upgrade timing, migrations, or production planning, please contact our Support team.

‍