Product update: Ricksoft’s full app portfolio completes migration to Atlassian Forge

We’re marking a milestone our engineering team has been working toward for months: every app in the Ricksoft portfolio has now completed migration from Atlassian Connect to Forge.

It’s not a new feature you’ll notice in your day-to-day workflow, but it might be one of the more consequential changes we’ve made to how our apps are built, because it’s about how your tools stay dependable, secure, and supported for years to come.

What is Forge, and why does it matter?

Forge is Atlassian’s current platform for building Jira and Confluence apps, the successor to Connect, the platform most Marketplace apps, including ours, were originally built on.

Forge apps use Atlassian’s security model and authentication by default, instead of the older approach Connect relied on. Depending on an app’s architecture, that can mean running entirely on Atlassian’s infrastructure, or securely connecting to backend services a vendor manages through a capability called Forge Remote, we use whichever fits each app best.

Either way, it’s a tighter, more modern integration with the products you use every day, with stronger default security and access to new platform capabilities as Atlassian ships them. If you want the deeper technical explanation, Atlassian has a good breakdown here →

Atlassian has also set a clear timeline for retiring Connect: apps still running on it will stop receiving updates and security patches once Connect reaches end of support on January 31, 2027.

Should you be worried? No — here’s why

If you manage Jira or Confluence for your team, you’ve probably seen a warning about this in Admin Hub, or had it flagged during a security review. It’s a fair thing to ask about.

For any app in the Ricksoft portfolio, the migration is already done. Not partially, not for a few flagship apps, but across our entire lineup. There’s no app in our portfolio still running on a platform Atlassian has scheduled to retire.

One quick thing worth checking on your end: if Atlassian Administration shows an update available for one of our apps, go ahead and apply it, that’s what moves your specific instance onto the new version. Atlassian rolls most of these updates out automatically, but some need a manual click, since Forge apps request permissions differently than Connect apps did. That’s a standard Atlassian approval step for any app, not something specific to us.

How to update, in under two minutes:

1. Go to Atlassian Administration and select your site.
2. In the left-hand navigation, select Apps, then Connected apps.
3. Look for a Ricksoft app with an UPDATE status next to its name.
4. Click the app’s action button, select View app details, then Update.
5. Review the updated capabilities, then confirm.

Full walkthrough with screenshots: Atlassian’s guide to updating apps →

Why this is a good thing for you

Beyond simply avoiding disruption, moving to Forge brings real, tangible benefits:

Stronger security by default. Every app now runs on Forge’s security model (Atlassian-managed authentication and permissions) instead of the older approach Connect used, regardless of whether an app runs fully on Atlassian’s infrastructure or securely connects to services we manage.

Faster compliance reviews. Because Forge apps inherit a meaningful set of Atlassian’s own SOC 2 controls, security and procurement teams often move through app reviews faster.

A platform that’s actively evolving. Atlassian is investing in Forge, not Connect. Staying current means our apps can pick up new platform capabilities as they ship, instead of falling behind.

One less thing to track. You don’t need to monitor our migration status or plan around it, it’s already behind us.

From our team

“Every team running one of our apps is trusting us to keep it secure and out of their way, and that’s the real reason this mattered to us.

Forge gives us stronger security by default, and puts us on the platform Atlassian is actively building the future of Jira and Confluence around, not winding down. We didn’t do this to check a box before a deadline. We did it so our customers never have to wonder whether the tools they depend on are still being looked after.”

Raziman Dom, Head of Product at Ricksoft, Inc.

“This milestone is bigger than a technical checkbox. It’s a statement about how we plan to operate going forward: staying ahead of platform shifts instead of reacting to them, so the apps our customers depend on remain secure, evolve alongside Atlassian with new capabilities, and continue to be a dependable choice for years to come.”

Sean Osawa, CEO of Ricksoft, Inc.

Thank you

This kind of change doesn’t happen without the trust our customers place in us to keep their tools running. We don’t take that for granted, and we’re glad to have this one fully behind us, so we can keep our focus where it belongs: building things that make your work easier.

Want the technical detail on what Forge means for your security and compliance posture specifically? Visit our Trust & Security page.

Not using Ricksoft apps yet? Explore the portfolio on the Atlassian Marketplace.