### Problem to solve Creating new issues requires understanding guidelines and appropriate product (see https://about.gitlab.com/submit-feedback/?nav_source=navbar), which raises the bar to filing them. To lower that bar, I proposed the creation of a nav bar button that automatically opens the correct issue tracker (i.e. autodetection of product), specifies the appropriate template (e.g. bug/feature), as well as adds a label for the appropriate team (based on owner of current UI page). ### Intended users All personas would use this button. ### Further details Benefits: * Quicker feedback on bugs/features, especially for newer users * More accurate labeling for faster visibility by the development teams ### Proposal Add button on the RH side of nav bar:  ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references