Hi @ibuchanan
This method of “… report them to Developer Support, use the “Bug” request type…” etc, especially the “We will actively work on resolving any blockers” sounded very good initially. I’d love to "log them, and then “watch, vote, and comment”, but it turns out that you can’t even get to this point very easily.
I want to share my experience with this, so you can add color and others can manage expectations.
We reported 3 important gaps on the 9th of October that are critical for us to move to v2. My expectation was that those will be added to the list ASAP, and we can rest assured that they will be worked on.
The reality is that those are still not added to the list. Ashish and his team are currently looking into those, trying to understand and recreate our use cases. This is fine, but not as a prerequisite for adding them to the list!
What I would like to express is that this sends the message of “instead of adding to the must-do list, we will first take a long hard look at your request, and if we can’t convince you to change it or dismiss your request in any way, then we will MAYBE add them to the list”.
Right now the process of reporting gaps leaves us with great uncertainty about the outcome and Atlassian’s real intentions.
6 Likes
@levente.szabo,
I’m willing to look into “optimistic tagging” with support and the Confluence team. That would put your items “on the list” sooner, letting issue status convey whether the issues are “accepted” (ie understood and reproducible).
That said, when I put the tone of your post aside (on the assumption that we can address that by tagging sooner), I’m still left with your critique that our standard practices leave you feeling uncertain. So other than my superficial procedural fix, what do you recommend?
1 Like
The next responsible step for the Confluence API team is to run roundtable discussions with the community.
Thanks, Ian. About general practices, I really can’t add anything to what already has been said by others in this and other threads.
I would recommend putting the reported bugs on the list sooner to assure the vendor that their blocker issues are registered “officially” by Atlassian, and will be addressed.
With the update provided in Confluence REST API v2: Update to v1 Deprecation Timeline, I’m going to ask the community to focus on that topic so that we’re all operating on the latest update. Since so much of the community concerns were based on timing, I’m going to close this thread.
Please understand that closure is not an assertion that all questions or problems were addressed. My main concern is that we don’t fragment feedback in too many places, and that it gets to the right people. If there are outstanding questions please ask on the new topic. Or submit a v1-vs-v2 gap to developers support.
2 Likes