[Bug] Quick action failure : `/relate` not working in description field at the creation of the issue or incident
Summary
According to https://docs.gitlab.com/ee/user/project/quick_actions.html
The following quick actions are applicable to descriptions, discussions, and threads. Some quick actions might not be available to all subscription tiers.
/relate
quick action not working if included in the initial issue description field
Steps to reproduce
- Choose a project where you have access,
- go to the "New issue" creation screen, with an already existing issue (for example
#1
) - Choose a title and in the description field add :
some text
/relate #1
- Click on "Create Issue"
=> the newly create issue is NOT linked with the referenced issue.
Additional Notes : this works when it is not done at the create Issue steps :
-
OK : If you edit the description field and re-enter exactly the same quick-action, the link IS created.
-
OK : If you add exactly the same quick action in the comment, the link IS created.
-
KO
🔴 : This is quick action is only failing on the create issue action.
Example Project
https://gitlab.com/comeh/gitab_features_tests_public/
What is the current bug behavior?
/relate
quick action is not run on the "Create Issue" action, but it is interpreted (since the quick action is removed from the Description field).
What is the expected correct behavior?
There should be a new link added to the "Linked issues"
Relevant logs and/or screenshots
This bug happens on GitLab.com
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
This bug happens on GitLab.com
Expand for output related to GitLab environment info (None)
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
We were using this feature successfully before Gitlab.com was in 14.x