Followup: Create Merge Request ID documentation and link it from Toolbar
Problem to solve
Usage of the Visual Review tool is lower than expected. We are hypothesizing that this is because it is too hard to use / not clear on how to set it up / not providing the value users think it should.
We currently provide no documentation towards the user as to why they should provide their MR ID and how they could potentially automate this process when coming into the visual review tool from the client side. We think this will help users to add MR ID and get more value from the feature.
Intended users
Further details
This is a followup to https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30481#note_189891845.
Proposal
Create a section in the Review Toolbar docs that speaks directly about the three ways to provide the MR ID (hardcoded, dynamic in script, through the form itself) and then link it to the form label in the review toolbar.
Link links to documentation explaining why we need the merge request ID and where the user can find it.
We still need to link towards that from the MR input state. The copy 'merge request ID' should act as the link anchor.
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
Any tracking of this issue is pending completion of #11944 (closed).