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.