"Provide feedback about this article" form froze (somehow)

This is a usability issue so it's important. Not because it stalls the system but because it stalls the user.

I'm having trouble to find out how to do things in Bitbucket so I opened a help page and from there goy into the tutorials page https://confluence.atlassian.com/bitbucket/tutorials-755338051.html\\
But this problem might attain all Bitbucket pages.
The tutos page has a "Provide feedback about this article" link. I clicked and a form opened so I wrote the text you can find below the "====" and clicked "submit".
The form got disabled and it stayed like that fr a long while.
The problem is that it didn't say nothing, it gave no feedback, like "thanks, we'll trash your comment soon" or whatever.
I don't know if Bitbucket received my comment or not, and meybe will never know.
This is the equivalent of telling something to somebody else and getting no acknowledge, just an inexpressive face for as long as you want. Wouldn't it be enraging?
Maybe the one who designed this interaction bit knows that the comment is filed and will be reviewed, but I don't. The designer designed for himself.

====
I can't find my way inside Bb.
I have a working repo and want to add bug tracking, which I was unable to do.
Apparently I need to create groups and a team, it isn't clear to me how to do it.
I ask myself if it's a feature only available for paid accounts, but it's not said anywhere.
I think you have an usability issue here.
Bb is facing a massive migeation from GitHub due to its purchase by MS and should hone these issues ASAP in order to capture more customers.
You need an usability guy, but not the usual one raised in the graphical design fields (it seems you already have one).
You need an UX guy from the engineering side, like most of the Internet usability heroes most of them engineers.
As such I struggled with the design-oriented types. They happen to not understand in full the interaction design side. With good interaction you don't need cute design, especially for the nerd customers we are, albeit it's a plus.

Usually the issues like the one I'm having arise from interaction design done by a good engineer that knows a lot about the underlying applications.
Such designs give for granted a number of knowledge bits that are obvious for the engineer but not for the newcomers (like me).
As nerds we should be able to dive into the engineer's mind (we are like-minded), but I'm failing to do so. Actually, the solution is to have an engineer diving into the user's minds.