Give Connect App a New Life on Forge Before Connect Sunset (No Coding Needed)

[#1]

If your team relies on Jira apps from the Marketplace, here’s a warning: Atlassian is ending support for Connect by the end of 2026.

Many popular Marketplace apps are still on Connect, and if their vendors don’t migrate them to Forge, they may stop working. That could disrupt critical workflows, dashboards, or integrations your team depends on daily.

This isn’t just a future concern - it’s a ticking clock for anyone who depends on apps that aren’t Forge-ready yet.

---

The Problem with Connect Apps on the Marketplace

• End-of-support risk: Connect apps that don’t migrate will lose compatibility with Jira Cloud.

• Uncertainty for your workflows: Features your team relies on may stop working overnight.

• No direct replacement: You can’t just “install Forge version” if the vendor hasn’t updated it.

For teams relying on these apps, the options are frustrating: wait for the vendor, find alternatives, or manually recreate workflows.
You can check migration status via this link - > https://www.forge-apps.com/

---

 Recreate Apps Yourself on Forge - no coding required

What if you didn’t have to depend on vendors at all?
Forge Apps Generator allows you to recreate the functionality of app - directly on Forge.

Even if the app already exists on Forge, you can use Forge Apps Generator to build your own version - tailored exactly to your team’s needs. Customize dashboards, trackers, and tools exactly how your processes work, without waiting for the vendor’s roadmap.

Whether it’s a dashboard gadget, progress tracker, workflow automation, or integration, you just describe what the app does, and Forge Apps Generator builds it for you.

• No coding or scripting required

• Fully compatible with Forge and Jira Cloud

• Ready for deployment instantly

How It Works

1. Describe your app: “I need a dashboard that shows story points by epic across projects,” or “I want a team capacity planner that updates in real-time.”

2. Forge Apps Generator builds it: Your description turns into a fully functional Forge app or dashboard gadget.

3. Deploy immediately: The app is ready for your team to use—no developer, no complex setup, no risk of future Marketplace app discontinuation.

 Bring Any Marketplace App Back to Life—or Make Your Own Version

• Custom Progress Trackers: Recreate specialized trackers from Connect apps that aren’t moving to Forge—or make your own with additional KPIs.

• Team Dashboards: Build dashboards that consolidate the views your team relies on daily—or redesign them to suit your workflow.

• Resource Planning Tools: Rebuild capacity planning or workload management apps before they become obsolete—or create your own with extra flexibility.

• Cross-Project Monitors: Track issues, KPIs, and metrics exactly the way your team needs—even if the original app disappears, or even if it exists on Forge but doesn’t fully fit your process.

Why Forge Apps Generator Is Your Insurance Policy

The end of Connect doesn’t have to mean lost functionality or broken workflows. Instead of waiting for vendors to migrate—or leaving your team stranded—you can take control of your tools.

Forge Apps Generator ensures:

• Continuity: All critical Marketplace functionality recreated on Forge

• Customization: Build apps tailored to your team, not limited by generic app settings

• Future-proofing: No worries about end-of-support or abandoned Connect apps

• Full control: Even existing Forge apps can be reimagined as your own custom version

 Don’t let your workflows be interrupted by end-of-support deadlines. With Forge Apps Generator, you can rebuild any Marketplace app you depend on, improve it, or even create your own custom version, without writing a single line of code.

Your team’s Jira experience stays seamless, while you gain full control over your tools.

[Ulrich Kuhnhardt _IzymesCo_]

"May stop working .."? How so?

[Matt Doar _Adaptavist_]

Erm, how does the app do things that Forge cannot do yet?

"you can rebuild any Marketplace app you depend on, improve it, or even create your own custom version, without writing a single line of code."

So I'd take that with a grain of salt!

[Jens Schumacher - Released_so]

It's great that you guys wrote a simple Forge app generator. But creating FUD (fear, uncertainty and doubt) is not the way to market in the ecosystem.

No successful app will just "stop working". Not only do the customer's workflow depend on it, but the vendors livelihood. That very livelihood is a much better insurance policy than an unsupported app generated by an LLM wrapper. 

Besides, the claim that this app can "recreate the functionality of any app" is vastly overstated as @Matt Doar rightly pointed out. 

[Jimmy Seddon]

Just to add some additional transparency here, if the app above makes a new forge app for you to deploy for your own company. Starting  Jan. 1st 2026, Forge is introducing a new pricing model:

https://developer.atlassian.com/platform/forge/forge-platform-pricing/

Why am I mentioning this? Because if you deploy a Forge app that goes over that usage, you and your company will be on the hook to pay for the overage costs.

Just something to consider before jumping in immediately.

[Bryan Guffey]

I'm really curious - I've used LLMs to generate a lot of Forge code, and I'll tell you, they're not that great at it. If yours is truly that much better that it can generate any Marketplace app, I'd be curious - what LLM are you using, did you train your own, and what techniques are you using pre- or post-inference to improve the responses? 

[Olha Yevdokymova_SaaSJet]

Hello @Ulrich Kuhnhardt _IzymesCo_ 

Yes, any private Connect apps (custom apps not published on the Marketplace) will stop working if their functionality depends on features or updates that Connect no longer supports. Similarly, custom workflows or folders tied to Connect apps may also be impacted if the underlying app isn’t migrated to Forge.

Atlassian has confirmed that Connect will reach end of support at the end of 2026, and any apps that haven’t been migrated may lose compatibility with Jira Cloud. To ensure continuity, Atlassian recommends reviewing the migration guides and starting the move to Forge early:

• Connect End of Support: What It Means for Custom Apps and How to Migrate to Forge

• Connect End of Support Timeline and Next Steps

[Olha Yevdokymova_SaaSJet]

Hi @Matt Doar _Adaptavist_ 

This app is created based on your requirements in a prompt. Of course, everything depends on Forge’s capabilities — if a certain feature is currently missing, Atlassian allows you to submit a ticket for the missing Forge capability.

If you believe any of these capabilities are critical to your app, please:

• reach out to your Partner Manager,

• comment or vote for an existing FRGE ticket,

• or create a new FRGE ticket.

Forge Apps Generator lets you quickly create your own version of an app based on your workflow description, but the final result will always depend on what Forge supports.

More details here:

• Connect End of Support: What It Means for Custom Apps and How to Migrate to Forge

• Connect End of Support Timeline and Next Steps

[Olha Yevdokymova_SaaSJet]

Hi @Jimmy Seddon 

Thanks for the note! Just to add some transparency: if the app above creates a new Forge app for your company, starting Jan 1st, 2026, Forge will have a new pricing model:
Forge Platform Pricing

This means that if your app exceeds the included usage limits, your company will be responsible for any overage costs.

We believe that Forge pricing will be reasonable for most teams. Keep in mind, though, that developing your own custom app may cost more upfront, and you’ll also be responsible for supporting and maintaining it. However, it gives you full control and flexibility, especially as Connect apps reach end-of-support.

[Olha Yevdokymova_SaaSJet]

Hi @Bryan Guffey 

We just released the first version and are continuously improving it. As an Atlassian Marketplace app developer with experience building 10+ apps, we’ve brought our expertise in Atlassian app development to make the LLM better at delivering meaningful and usable output for Forge apps.

We’re currently using Anthropic, customized and fine-tuned for this purpose. We’d love for you to try it and share your experience—it would be really valuable for us to get your feedback!

[Olha Yevdokymova_SaaSJet]

Hi @Jens Schumacher - Released_so 

We just released the first version and are continuously improving it, and we truly believe in the potential of AI development. Of course, not all apps will simply stop working—but as Atlassian notes, if your app relies on a Connect module that reaches end of support, it’s effectively ‘use at your own risk.’

Connect consists of a collection of capabilities (JWT, descriptors, etc.), modules (web items, web panels, macros, etc.), and extensibility (APIs and JavaScript APIs). All of these components will be in scope for end of support.

So while most apps will continue functioning, there is a risk for apps depending on deprecated Connect modules once support ends. Our goal with Forge Apps Generator is to give teams a way to recreate or adapt critical functionality in Forge if needed, while we continue improving the tool and exploring what AI can do in this space.

More details here:

• Connect End of Support: What It Means for Custom Apps and How to Migrate to Forge

• Connect End of Support Timeline and Next Steps

[Jens Schumacher - Released_so]

@Olha Yevdokymova_SaaSJet this is what bothers me about your post. You imply that using apps built on Connect poses a risk, which is not the case at all.

There is a straightforward path to Forge for most Connect apps, but it depends on the vendors' priorities and when they choose to migrate. Just because they are on Connect right now doesn't mean they don't have plans to migrate. 

Most apps that are still being maintained will transition to Forge, despite your portrayal of doom and gloom to sell your app. 

[Ulrich Kuhnhardt _IzymesCo_]

I am confused now @Olha Yevdokymova_SaaSJet  - are my connect apps going to stop to work or is the platform rather "reaching end of support, and effectively ‘use at your own risk.’"?