Deprecation of V1-Api Confluence – Major concerns

[ibuchanan]

@ucchishta.sivaguru,

@ucchishta.sivaguru

Let me know if there’s a relevant topic for me to raise this

The resolution for RFC-19 explains how anyone in the community should raise a specific gap:

@AshishShirode

Future Feedback: If you come across any gaps in REST API v2 in the future, please report them to Developer Support . Use the “Bug” request type and be sure to mention that gap is related to the v1 deprecation. We will actively work on resolving any blockers. This process is more transparent and your report will be added to the tickets queue . Going forward, we will not be monitoring the developer community for additional v2 feature gaps posts.

I realize this does not address some of the other concerns raised in this thread about pace/timing of the deprecation, if not other aspects of our ecosystem policy. I am continuing to work with the Confluence team to try to get answers. But please do not let that uncertainty get in the way of logging specific gaps. In the RFC, the Confluence team has already committed to closing the gaps as tracked in CONFCLOUD. I know that I so often say, “please watch, vote, and comment” about issues, but this case already has “special dispensation” for those issues with the rest-api-v2. So please log them, and then “watch, vote, and comment” to deepen the understanding and improve the prioritization.