Tempo is moving to Forge - what you need to know

[#1]

Hi all,

Less than 24 hours ago, we received the following email notification that Tempo is moving to Forge:

---

We're upgrading Timesheets, Capacity Planner, and Financial Manager to run on Forge, Atlassian's modern cloud-native platform. This is a significant infrastructure change, and for most users the experience inside Jira will feel the same. But there are a few breaking changes that might apply to you.

Why we're moving to Forge

Atlassian is evolving how Marketplace apps are built, and Forge is where all new platform capabilities are being developed: deeper security controls, performance improvements, and AI integrations through Rovo are all tied to it.

When will my instance move to Forge? How will I know?

The migration to Forge will begin on Tuesday 31st March and roll out gradually over the following weeks. We’re not able to offer opt-outs as this is mandatory for compatibility with Atlassian Cloud.

Once your instance has been migrated, you’ll receive an in-app notification confirming the change.

---

Has anyone received any prior notifications? Considering the impact for Timesheets , Capacity Planner, and Financial Manager I'm quite suprised by this last minute announcement.

I'd like to know from Tempo Software if there were any prior communications/notifications sent.

[Shawn Stevens]

I was wondering the same thing.

[Raul Pelaez _QUABU SOLUTIONS_]

More info here: https://help.tempo.io/timesheets/latest/expected-changes-in-timesheets-on-forge

[Dmytro Rudenko _ Release Management]

We also migrated Release Management to Forge back in March. The technical part went fine. But then I sat there as the person responsible for communicating this to our customers and thought… do they actually need to know? The UX didn't change. Nothing broke. The improvements are all infrastructure-level stuff that matters to Jira admins and security teams, not to the person opening the app every morning.

We ended up sending a detailed announcement anyway, because transparency felt right. But I honestly don't know if more than 10% of recipients understood why they should care. "We moved to Forge" means nothing to someone who just wants their release dashboard to work.

Which brings me to the selfish question: has anyone actually seen a measurable impact from migrating early? More installs, better Marketplace visibility, anything? Or is it purely a "stay on the platform or get kicked off" situation with no upside beyond survival? We migrated months ahead of the deadline and I'm still trying to figure out if there's a marketing story in that or if it's just table stakes that nobody notices.

The Tempo situation is wild though - less than 24 hours notice for a major infrastructure change on an app that touches timesheets and billing. That's brave.

[Kathryn Vargas]

Thank you for raising this, @Dave Mathijs. It's a fair question and deserves a direct answer.

To clarify: the March 30 email was the final step in a communication chain that began in June 2025, when we published a blog post announcing the general move to Forge. As the transition approached, we ramped up outreach in March: documenting the behavioral changes in detail, adding in-app banners linking to our Expected Changes documentation, and publishing a second blog post. The email closed out the chain.

That said, we recognize the email itself arrived too close to the (then) start date. The earlier channels did the job of explaining the why and the what, but they mostly reach people who are already using the app day-to-day. The direct email was the piece specifically designed to reach admins and billing contacts, but one day before rollout was too late. For something with this kind of impact, we could have done better and apologize for the pressure it put on your teams.

On the impact itself: moving to Forge has resulted in some behavioral changes in features that interact with Jira, specifically around JQL filters, Jira automations, and the Tempo panels in the Jira issue view. These stem from fundamental differences between the Forge and Connect frameworks. Importantly, these changes only affect users who rely on those specific features. For most users, the migration won’t be felt.

For those who will feel it, we've prepared recommendations for how they can minimize the impact. We've also built a new tool — Broken JQL Filter Finder — to help anyone affected identify JQL filters that need fixing post-migration.

Since the March 30 email, we've hosted a webinar walking through the changes, updated the tentative automatic rollout date to June 15, and revised our recommendations on migration to reflect the timelines Atlassian has provided for addressing the key behavioral changes. You'll also receive an in-app notification once your instance has moved.

We appreciate the community flagging this; it's exactly the kind of feedback that helps us communicate better.

Kathryn, Tempo Product Team