TL;DR As we approach Connect end of support in December 2026, Atlassian product teams are focused on delivering the remaining features you need to migrate. We’re in the process of building the roadmap that will take us through to end of support, and we want to ensure the features that matter the mos…

We have begun the review process for every ticket that has been submitted so far; I guarantee that your requests will be reviewed as well. Thankyou to everyone that is engaging and submitting their requests.

The real problem is that the Connect EOL deadline is completely artificial and is under full control of Atlassian and it’s up to Atlassian management to decide whether they want to actually deliver a decent development platform, or if they want to meet their made up deadlines without consideration f…

@rmassaioli what is the extend to which something is considered a Connect / Forge feature parity mismatch within the context of this effort? For instance, the issues raised by @tbinna in Forge platform gaps and new API rate limits are valid blockers for migrating to Forge, especially in combination …

If you can demonstrate that there is something you can do in Connect, that you can’t do in Forge (even with Forge Remote), and can explain what the consequence of that is for your App/Business, then I would strongly recommend that you follow this process on those FRGE tickets. We are more than happ…

Hi @rmassaioli . Our eSignature (connect) app does support and is actively used by customers via the Jira mobile app. Is there any value in us submitting/escalating FRGE-1492 for consideration? Trying to get a sense if there is an Atlassian decision to not enable Forge on Jira mobile. Thanks Ch…

Yes. I think that every ticket that you can do in Connect, that you can’t do in Forge (via any means), should be submitted for review. I think that Mobile App support for Forge Apps qualifies.

Connect framework: In case of site “base_url” change, we used to get install event, Where we could update the base_url of a customer in our database. Forge framework: In same scenario we don’t get the install event. If we don’t get the base_url then How to identify the changed base_url ? We have a…

project = FRGE AND (reporter = currentUser() OR issue in watchedIssues() OR issue in votedIssues()) AND resolution = Unresolved ORDER BY updated DESC Finding critical blockers I reported back in 2022 that haven’t been touched. And again I’ll add that I think it’s lunacy to migrate while versioni…

We are marking the work items important to us according to the process announced here, and it is good to see some transparency going on here. However, it does seem odd to say the least that migration blockers are only beginning to be collected with a month remaining until the date of the Connect r…

I can’t request a review because I don’t have a Connect app, but I imagine that the lack of layout customizability is a blocker for many Confluence apps: https://ecosystem.atlassian.net/browse/FRGE-960 Related ticket: https://jira.atlassian.com/browse/CONFCLOUD-81631

The Atlassian Developer Community

Tell us what you need before Connect EoS: Submit your critical migration blockers

Announcements