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.