Reported gaps are being ignored. This has been the case for about two years now. Plenty of posts in the forums of people having their parity bug reports triaged and dropped.
This happens before a CONFCLOUD ticket is created. If one is created, the priority often gets downgraded, switched from bug to suggestion, and eventually dropped or ignored.
Developers were assured that there would be 100% feature parity before any 6 month deprecation date was set. This promise has been broken many times now.
v1 expansion queries are woefully absent or inadequate in v2. One call in v1 now requires multiple calls, and often exponentially more calls with abysmal performance.
Something as simple as uploading an attachment requires a v1 call while fetching that same attachment requires a v2 call. You can get/set content properties using the JS API but those exact same calls in the REST API are being deprecated and now require four calls instead of one. That’s the tip of the iceberg.
None of this makes any sense whatsoever. Most developers I know have held off migrating in the hopes that Atlassian would address these and the many major flaws.
I’ve started dumping every problematic endpoint I come across into a support ticket, but I don’t expect these will ever be fixed. I know I will simply be told “no, we’re not doing expansions for that” and a CONFCLOUD ticket will not be created. No ticket, no gaps lol.
eg I’m staring at this v1 call right now trying to workout how to possibly fetch the same data in v2 without needing to make 100s of calls to replace it: /rest/api/content/{id}/version?expand=collaborators.users