<!--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=18088) </details> <!--IssueSummary end--> - As confirmed with Slack, it is a good practice to send back a loading state Slack response after a slash command has been executed. - For example, after you create an issue with a slash command, a loading state message could be `Command received. Creating issue.` - And then when the issue is created, then GitLab sends back the JSON payload to display the full message inside Slack. - It _should_ be possible to replace the loading message with the issue display message once it arrives: https://api.slack.com/methods/chat.update or https://api.slack.com/methods/chat.delete. This is the design practice to follow per Slack.