@EdmundMunday I’m quite concerned about the timelines and expectations for partners migrating their apps to Forge, especially given how heavily we rely on Connect features that still need to be ported over before we can proceed on our end. How can we possibly update if the functionality is not there?
So far, in addition to what have already been reported by others here, I’ve identified the following missing functionalities that our app uses, which are available on Connect, but either not supported on Forge or lack a clear migration path:
- Conditional rendering using application properties
- Groups Endpoint
- Subscribe to repository webhooks
- App merge with branch restrictions - BCLOUD-22400
We need a better support from Atlassian on the migration process, in terms of communication and technical support. Simply saying that Atlassian is committed, without providing effective support and not porting the features needed, is meaningless.
Can we please get an update and dates when these functionalities are expected to be available? Are the EOL dates being pushed back since the feature parity is not there yet? The only dates Atlassian has communicated so far are when things will reach EOL or will stop working.