Skip to content

Fix /confidential /set_parent quick action interaction

Matt D'Angelorequested to merge
531197-new-issues-not-linking-to-epics-when-using-quick-actions into master

What does this MR do and why?

This MR resolves an issue where the /confidential and /set_parent quick action params are used in conjunction on a work item. Previously, the /set_parent check for confidentiality would not consider the case where the /confidential quick action was also passed in the same template. In this case, since the child would also become confidential, we should allow it to be assigned to a confidential parent.

References

Screenshots or screen recordings

Not provided

How to set up and validate locally

  1. Create a confidential epic, and note the epic reference. In this case, we'll assume it's &4
  2. Create a work item template (.gitlab > issue_templates > Template.md) with the following contents:
/confidential
/set_parent &4
  1. Create a new work item issue, and assign it the template created in the step above
  2. Observe that after the work item issue is created, it's confidential and assigned to epic &4

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #531197 (closed)

Merge request reports