Today, we started seeing this banner in most of our UIs. This is super invasive and scaremongering, especially since we are in the process of moving to Forge. I’m not aware that this has been announced somewhere (RFC or changelog) and it gives us no possibility whatsoever to provide documentation for this.
Also, this is not what I’d consider as “Connect modules will continue working but unsupported”. How in the world is this being considered as “working” - this is an effective and total deprecation. Not that it matters to our personal plans, but this is not as announced.
Is this already rolling out to customers? We need to inform support staff about this, this is totally unacceptable. This also kills all potential new trials, since no customer will buy an app after seeing such an announcement in app…
I’m not seeing it on all Confluence instances, so this doesn’t seem to be rolled out completely yet.
I do agree that this just spreads fear among our customers while we are trying hard to migrate our apps to Forge. This does not help our support staff either.
Please do not roll out this banner to customer instances.
I’m echoing these exact concerns. We started observing this banner across our Jira App UIs today as well, and the impact is highly alarming.
While our team is actively in the middle of our migration to Forge, our deadline is still months away in December. Showing a heavy-handed banner like this right now signals a massive, unwarranted “wrong trust signal” to our existing customers. It actively erodes the trust we’ve spent years building, long before the actual deprecation timeline requires it.
Like @tobias.viehweger mentioned, this completely disrupts the conversion of any new trials. No prospective customer is going to evaluate, let alone purchase, an app that triggers invasive “unsupported” warnings directly inside the UI.
Atlassian, we need immediate clarity:
Can this banner be suppressed or customized for vendors who have documented active migration paths?
Was this rollout explicitly communicated to vendors beforehand?
This goes far beyond “Connect modules will continue working but unsupported”—it actively damages our current business while we are doing the work to transition.
We can also confirm that we are starting to see this banner / info message across our Connect-on-Forge and Connect apps.
It would be great if this banner doesn’t show for apps that are transitioning to Forge, and are already Connect-on-Forge. Would it perhaps be possible to hide this banner for Connect-on-Forge apps that are receiving frequent updates as they are still migrating over modules.
IMHO this should only be shown after we’ve had the chance to submit our migration status and only for apps that have not yet responded or responded with “we’re not going to migrate”. Showing these banners now is premature and confusing.
Thank you for raising this with us. As per our previous comms, this messaging should only be visible for non-marketplace apps. We are actively reviewing this and rolling the change back.
Thanks again for raising this. We will take some time to re-clarify what happened here and ensure that this only rolls out to non-marketplace apps.
I wanted to follow up here about what happened. Firstly, I want to apologise for any surprise or frustration this caused. I want to be transparent about what happened and what we’re doing about it.
What we were trying to do:
As Connect approaches end of support, we have an obligation to give customers advance notice when an app may be running on an unsupported platform. Our plan was to roll this messaging out to non-public apps first, deliberately giving our Marketplace partners more time to migrate before customers started seeing these notices.
Alongside that, we enabled the messaging in the Developer Canary Program (DCP) so enrolled partners and developers could:
See the exact messaging customers will see and give you time to adopt the new module in your manifest before this messaging goes live
The intent was to strike a balance for both customers and partners, whilst giving you more space to migrate across to Forge and submit your migration status.
What went wrong:
Unfortunately, the communications we had planned to give partners advance notice of this change going live in canary instances did not go out as intended.
What you need to know:
This messaging was scoped to canary tenants only, we don’t expect anyone outside of this cohort to have seen this messaging
To address any concerns that you may have had, we pre-emptively raised an incident and there is a status page update you can point towards if you have any affected customers reaching out.
What will happen now:
For non-public apps:
Today, we will restart the rollout of this change to non-public apps only in production*.* This will only include messaging in the admin experience and no end user notices. Development apps using a Connect app key which is not the same as the marketplace listing will see this messaging.
For public apps:
We will send out a changelog notice 1 week prior to us enabling this messaging for those enrolled in the developer canary program for early awareness. This will include messaging in the admin experience only. It will only appear for tenants enrolled in DCP. We are targeting a release date of June 2nd.
We will issue another changelog notice at least one week before this messaging goes live on production instances, giving you time to adopt the new module. We will target the rollout to start in July and gradually extend it to all public apps over three months. From September onwards, all customers with apps installed that use any Connect features will see this messaging in their admin experience and as end user notices in iFrames. Again, we will proactively communicate when the time comes to ensure you’ve made these changes and can share your migration plans with customers.
We apologise for any confusion or concern this caused, that was absolutely not our intention. We really value the partnerships we have built with this community and appreciate the effort you have put into your migrations.
Thank you for the detailed explanation and transparency around the root cause and your further plans!
I strongly believe that showing a warning banner for all apps at latest in September that still contain Connect modules is problematic and will unnecessarily damage customer trust.
Atlassian has communicated that Connect will move out of support at the end of the year. As Marketplace Partners, we have aligned our migration plans, customer communication, and product roadmaps with that target date.
If an app is still within the officially communicated support window, actively maintained, and has a migration plan aligned with Atlassian’s timeline, showing a warning such as “This app might stop working soon” creates the impression of an immediate risk where there may not be one. This can lead to unnecessary concern among admins and end users, increase support load for partners, and damage trust in apps that are still operating as expected.
I fully understand the need to inform customers and admins about the transition away from Connect. However, the messaging should distinguish between:
apps with no migration plan,
apps with a published migration plan aligned with Atlassian’s deadline,
and apps that may actually become unsupported soon.
A generic warning banner before the communicated end-of-support date does not reflect these differences and risks creating avoidable uncertainty.
From my perspective, Atlassian should first give partners a way to publish their migration status and plan, and only show customer-facing warnings where there is no clear migration path or where the app is actually at risk of missing the support deadline.
Can Atlassian please specify where this obligation is stated?
There is a strong difference between a legally binding obligation (which this wording suggests) and Atlassian moral views / values with regard to how it should communicate with customers. Either this is a statement of fact, or it is a mere opinion. If it is an opinion, Atlassian still has a right to have it, but I would suggest that given her reputation of selectively applying her values Atlassian might want to use a less rigid wording.
So, if there is such a legal binding obligation, it would help if you can share this so that we can use this in our own communications. Otherwise, please adjust the wording from “we have an obligation” to “we believe it is appropriate”.
Is this app warning coordinated with resolving the Connect to Forge migration blockers? We’re waiting for Atlassian engineering to deliver more Connect parity, and it seems these warning banners do not take this into account.
Another problem is the one week rollout warning in the Changelog. This is not sufficient, and I would expect at least a 3 months warning. The timeline of the Connect end of support is known since last year, and changing messaging midway disrupts our migration efforts and customer trust. I would expect that Atlassian has an obligation to fully support their stated Connect to Forge migration tooling, and also has an obligation to commit to their own stated timeline.
At no point has that ever been communicated to partners. Are you serious?!
Atlassian is going to forcibly plaster public marketplace Connect apps with end-user warning messages THREESIX whole months before EOS and you’re only informing partners now, in this thread exposing a screw-up, and with THREE ONE month notice?! Surely you’ve miscommunicated something in your reply here?
!!!
The date at which you forcibly plaster a warning message on an app is the date which developers would consider to be an absolute and final hard migration deadline which needs to be communicated clearly with precise dates and abundant forewarning. If that’s not obvious to Atlassian it speaks volumes.
EOS (end of support) has always been communicated as a date beyond which platform support ends but apps still function as ~expected until some unknown EOL date. Warning messages for EOL (end of life) would make sense because the apps would stop functioning completely.
Warning messages applied prior or shortly after EOS could risk EXTREME LEGAL DAMAGES to partners if, for instance, customers cancel their subscriptions due to the unnecessary scaremongering of these warning messages.
The migration blockers are widely documented despite the ongoing gaslighting.
Hell, I’m still waiting for the fundamentals of versioning and updates to be finalised:
Let that sink in: versioning is not yet finalised on Forge!!!
You’re force-ramming everyone to migrate to a platform that hasn’t yet sorted out versioning and which inevitably results in zombie apps. Truly unfathomable disaster.
Why exactly is that and where does this obligation come from? I am wondering about this, because it feels like an important precedent to set. If Atlassian feels obliged to warn customers that a Connect app will be unsupported in three months if the vendor does not migrate to Forge by then, would the same obligation be applicable to other cases as well?
To give some examples: Will Atlassian show the same warning on all Forge apps that use a runtime that will be outdated in three months time? Will a warning be shown on an app that uses an older React version that’s approaching End of Life? Or maybe apps that use @atlaskit/editor-core?
And what exactly is the benefit of showing this warning to customers when the platform is still supported, the end-of-support date has not been reached and the vendor does have a plan to migrate in time? Frankly, for everyone who cares about not alienating customers, Atlassian is moving up the EOS date for Connect to September 1st.
Hi @EshaaSood – A few requests to make this rollout more supportable for customers:
Would Atlassian please select a more specific date for the EOS of Connect? This entire time, I naively assumed the date was December 31, 2026. But looking back, I can see that was nothing more than an accidental assumption. Is support actually ending on December 1? December 15? What is it? Please select a specific date and include it in your customer-facing messaging.
Please do not roll out this banner to apps that have committed to migrating by EOS. Doing so inaccurately implies the apps will at some point use an unsupported platform. Nowhere in the new module documentation did Atlassian indicate that you would display “This app may stop working”.
PLEASE consider using less fear-mongering language. We all know that zero apps are going to magically stop working on the EOS date. (Unless Atlassian is planning something nefarious, which I trust you are not.)
