<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=9792) </details> <!--IssueSummary end--> ### Problem to solve Ability to create an issue directly from highlighted code/text in Web IDE. While doing manual code review from the GitLab Web IDE, allow the ability to select/highlight a piece of code in question, right click then select "Create new issue". A new issue opens up and the selected code is stamped into the issue description to further describe problem or action to take. ### Target audience - Parker, Product Manager, https://design.gitlab.com/research/personas#persona-parker - Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney - Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha - Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon <!--- For whom are we doing this? Include a [persona](https://design.gitlab.com/research/personas) listed below, if applicable, along with its [label](https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A), or define a specific company role, e.g. "Release Manager". Existing personas are: (copy relevant personas out of this comment, and delete any persona that does not apply) --> ### Further details <!--- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal <!--- How are we going to solve the problem? Try to include the user journey! --> ### 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 --> ### What is the type of buyer? (Which leads to: in which enterprise tier should this feature go see https://about.gitlab.com/handbook/product/pricing/#four-tiers ) ### Links / references