Dear Connect apps,
You were fast.
You were flexible.
You let vendors build almost anything, anywhere, however they wanted.
And for a long time â that freedom felt like progress.
This postcard isnât about pretending the transition to Forge was easy.
It wasnât.
For vendors or for users.
But itâs also not a complaint letter.
Itâs a year-end reflection â on what hurt, what improved, and why this change matters more than it first appears.
âď¸ Letâs start honestly: Forge migration comes with real pain
If you were around during a migration, you probably felt at least one of these:
âSome things just donât exist the same way anymoreâ
Not every Connect module has a perfect Forge equivalent yet.
Some UI extension points behave differently.
Some flows need redesign instead of simple migration.
From a user perspective, this can look like:
That frustration is valid.
âOur integrations suddenly became⌠complicatedâ
Forge places strict controls on outbound connections.
What used to be âjust connect to this external serviceâ now requires:
-
declared egress
-
explicit allowlists
-
architectural changes
For users, this sometimes meant:
Security improved â but not without friction.
âWe paid the migration cost, even though we didnât ask for itâ
Vendors rebuilt.
Users retested.
Admins revalidated.
Security teams reapproved.
All while the app mostly looked the same.
And yes â that can feel unfair.
đ Now the other side of the postcard: what actually got better
Once the dust settled, something quietly changed.
đ Security stopped being âtrust usâ
Forge apps run inside Atlassianâs infrastructure.
For users, this means:
-
clearer answers to âwhere does our data live?â
-
fewer unknowns during security reviews
-
stronger alignment with Atlassianâs compliance model
Not abstract security â practical, explainable security.
đ§ Permissions became understandable
Instead of broad, opaque access scopes, Forge enforces tighter, more explicit permissions.
That made life easier for:
Less âwe hope this is fine,â more âwe know exactly what this app can do.â
âď¸ Stability started to outweigh flexibility
Connect was powerful â but power came with variability.
Forge trades some freedom for predictability:
-
fewer environment-specific surprises
-
more consistent behavior across tenants
-
better resilience during Atlassian platform changes
đ The uncomfortable truth: this isnât optional anymore
Atlassian has been clear: by late 2026, Connect apps must move to Forge.
So this shift isnât about trends or preferences.
Itâs about the ecosystem maturing.
Forge isnât saying:
âBuild less.â
Itâs saying:
âBuild responsibly â in a way that scales for millions of users.â
 Our own Advent milestone
This month, we reached an important checkpoint ourselves:
Smart Forms for Jira has completed its Forge migration.
Not because it was easy.
Not because it was fast.
But because it was the right thing to do â for long-term security, trust, and alignment with Atlassianâs platform.
Like many vendors, we:
And now, the app runs fully on Forge â inside Atlassianâs cloud.
đ A year-end wish for everyone migrating
To users navigating change:
May your apps be secure, predictable, and transparent.
To admins and security teams:
May your reviews be simpler and your answers clearer.
To vendors rebuilding quietly behind the scenes:
May your migrations be steady and your users patient.
Dear Connect apps â
thank you for getting us here.
And welcome to a safer, calmer, more responsible Jira ecosystem.
Wishing everyone a secure end of year and a confident start to the next one. đâ¨