<!--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=396891) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Context <img src="/uploads/8e187ab2f622712efaf3ec395cc900b7/Screenshot_2023-03-16_at_14.27.40.png" width="300"> With the release of Saved Replies (currently being [rolled out](https://gitlab.com/gitlab-org/gitlab/-/issues/352956)), usage is bound to pick up. As the list of saved replies grows, so does the difficulty and the steps needed to select the right one. Perhaps we could facilitate the injection of a saved reply by not needing the dropdown in the first place. ### Proposal 1. Add an optional field to each Saved Reply: `trigger` 2. Whenever user types a pre-defined "trigger" word (eg: `;[triggerword]`) it would immediately expand to the full saved reply (Note: when `;` is detected, it could show an autocomplete like we do for emoji, issues, epics, or MRs) ``` ;suggNB ``` would transform to ``` **Suggestion (non-blocking):** ``` <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->