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.
If you were around during a migration, you probably felt at least one of these:
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:
missing panels
delayed features
âwhy did this change if nothing was broken?â
That frustration is valid.
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:
integrations paused or reworked
workflows adjusted
temporary gaps while vendors redesigned safely
Security improved â but not without friction.
Vendors rebuilt.
Users retested.
Admins revalidated.
Security teams reapproved.
All while the app mostly looked the same.
And yes â that can feel unfair.
Once the dust settled, something quietly changed.
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.
Instead of broad, opaque access scopes, Forge enforces tighter, more explicit permissions.
That made life easier for:
admins approving apps
security teams auditing access
customers explaining risk internally
Less âwe hope this is fine,â more âwe know exactly what this app can do.â
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
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.â
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:
rethought architecture
navigated limitations
rebuilt pieces instead of porting them
tested carefully to keep existing workflows stable
And now, the app runs fully on Forge â inside Atlassianâs cloud.
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. đâ¨
Olha Yevdokymova_SaaSJet
Product Marketing Manager
SaaSJet
Ukraine
23 accepted answers
0 comments