It feels pretty unfair for Atlassian to acknowledge that partners cannot migrate to Forge because Atlassian does not support their use cases, whilst also charging a premium for their failure to comply.
Perhaps I’m just a grumpy old hag with ancient morals, but I’d have trouble sleeping over this type of blatant opportunism.
Also one would hope the question has been asked internally: “at what point in time will the AI models and harnesses be able to perfectly migrate any Connect app to Forge in one-shot?”
If the migration deadline occurs before that point then Atlassian has wasted an unacceptable sum of partners’ time, money and resources for no reason whatsoever other than a lack of situational awareness.
At the very least, there should be a carve out for apps that have requested Connect EoS review on at least one FRGE ticket.
Atlassian knows which apps these are, as the EoS review submission required specifying an app that the issue impacts.
If partners are acting in good faith and are yet again* signalling to Atlassian the issues they believe are genuine blockers, and those partners don’t hear anything back from Atlassian regarding those issues until after the deadline; it seems only reasonable that those apps get an exemption from the higher take-rate that comes into effect in just over a week’s time.
(*this is after being repeatedly asked over many years to fill out countless surveys, questionnaires, watch & vote on FRGE tickets, and various other means of signalling to Atlassian any potential blockers)
For apps remaining on Connect that have not requested any EoS reviews, the revenue share increase can still take effect (on the assumption that these apps made no final attempt to highlight any blockers).
Atlassian has been aware of these FRGE tickets for some time. Some of the ones I have requested review on were raised over a year ago (usually gathering dust with a status of “gathering impact” or similar).
To Remie’s initial point, it seems unfair that Atlassian sat on these issues for years (while at the same time gaslighting partners by telling them that “most apps can migrate to Forge now!” when clearly they couldn’t), and despite all the previous surveys, votes & watchers, is still prepared to penalise those apps that are blocked or would need to materially degrade their functionality/UX moving to Forge.
In my passing discussions with the Forge team they made it abundantly clear that they did not agree with the penalty decision and had no say in the matter.
It’s the management layer above them who are many steps removed from the technical reality that are calling the shots.