Smart Jira Issue for Confluence has moved from Connect to Atlassian Forge

Smart Jira Issue for Confluence has run on Atlassian Connect since it first shipped — its own Node server, its own database, its own uptime to babysit. That’s now changed: all three macros — Smart Jira Issue View, Smart Filter and Children View, and the legacy static macro — have been rebuilt on Atlassian Forge, and the migration is live.

What actually changed

Nothing in how you use it. Same macros, same field picker, same shortcuts, same issue and filter embeds already sitting on your pages — they all keep working exactly as before. What changed is everything underneath the macro, not the macro itself.

Full backward compatibility

Every page that already has a Smart Jira Issue macro on it — box style, inline style, children list, saved filter — keeps rendering with the exact configuration you set up originally. We kept the old static macro alive specifically so pages built with it don’t need to be touched or re-inserted. There’s nothing to migrate on your pages, because we already did it for you.

Zero-hassle migration

Atlassian ties the new Forge app to the old Connect app through a succession key, so your existing installation and license carry over automatically. No re-install, no re-approving permissions, no re-purchasing, no gap in service. If you didn’t read this post, you likely wouldn’t have noticed the migration happened at all.

Runs on Atlassian

Because the app now runs entirely on Forge, it qualifies for Atlassian’s Runs on Atlassian designation. Your Jira data — issue fields, descriptions, custom fields, filter results — is processed entirely inside Atlassian’s own cloud, with no third-party server in the loop. If your organization runs a security review before approving Marketplace apps, this removes a question that used to need a longer explanation.

Full security, by construction

The old Connect app authenticated with a JWT shared secret and its own hosted datastore. The Forge app has neither: there’s no external server to breach, no app-managed credentials, and no OAuth tokens stored anywhere outside Atlassian. Every Jira call is made asUser() — scoped to the permissions of whoever is viewing the page — using only read:jira-work and read:jira-user. There’s no broader, app-level access to your Jira instance to worry about.

The same pricing

Your Marketplace subscription and pricing tier carry over unchanged. This is a platform migration, not a repricing — nothing changes on your invoice.

A couple of other things that come with it

• Off a platform Atlassian is retiring. Connect is on its way out across the Marketplace; moving to Forge means Smart Jira Issue keeps getting updates and stays fully supported for the long run, instead of being stuck on a deprecated stack.
• Atlassian-managed infrastructure. No more relying on our own server’s uptime — the app now scales and runs on the same infrastructure as Jira and Confluence themselves.
• One admin page, reachable from either product. Docs and support are now available as a proper admin page from both the Confluence admin console and the Jira admin console, not just a general page tucked into Confluence.

Do you need to do anything?

No. Existing installations, licenses, and pages all carried over automatically. If you notice anything behaving differently, let us know — otherwise, there’s nothing to do.

Want the details on how the field picker or filter view works? See the FAQ or the product page.