Connect End of Support extended to January 31, 2027

Announcements
, ,
1

Hey developers :waving_hand:

We’re extending the Connect end of support date from December 2026 to January 31, 2027, to give partners and developers more time to plan around the holiday period and annual planning cycles.

We’ve published a blog post with everything you need to know ahead of that date: the full migration path, what to expect after end of support begins, and guidance on publishing your migration plan to customers.

:backhand_index_pointing_right: Getting Ready for Connect End of Support - Inside Atlassian

Questions or blockers? Post here or check the Forge | Kanban board to see what’s already being tracked.

2

Eventually, we will begin surfacing your migration intent within app iframes.

Partners need an exact date. You still don’t seem to understand that this date is far more crucial to partners than the EOS date. Of course the logical decision would be to display iframe messaging long after the EOS date.

Also the current requirement to have a Forge app before you can communicate your migration plan to end-customers is clearly a cart-before-the-horse situation. Connect-only apps need a method to modify this message.

And please don’t waste everyone’s time with unnecessary bureaucracy as the EOS date approaches. eg I assume this email survey blastout is going to be an ECOHELP ticket for each and every app. You only need to send one ticket per partner.

3

Hi Esha,

Thanks for the update and acknowledging that there is still some work to do, since the last blockers are still in the process of being addressed. Unfortunately this does I not cover the most important impactful points for us right now when it comes to migrating:

  • Will the second revenue share change also move a month back?
  • Will the end-user messaging also be pushed back by a good amount? Current plans seemed to indicate September for end-user messaging.

We currently are in the process of evaluating an exact rollout timeline for our full Forge based manifest, since we have customers who, for example, rely heavily on things as mobile support which is just in the process of getting discussed by the Atlassian teams - ideally we wouldn’t like to force the update on them for 3 month, disrupting their workflows, only to have it available in time afterall…

Thanks

Tobias