[go: up one dir, main page]

Resolve "Follow up from "Sharding Key Investigation for work_item_hierarchy_restrictions table""

Matt D'Angelorequested to merge
568269-follow-up-from-sharding-key-investigation-for-work_item_hierarchy_restrictions-table into master

What does this MR do and why?

This MR addresses a follow up from the work in !203351 (merged), where we still reference the WorkItems::HierarchyRestriction in the quick action logic for work items. The change here instead updates this to reference the new WorkItems::SystemDefined::HierarchyRestriction model.

References

Screenshots or screen recordings

Not provided

How to set up and validate locally

The behaviour of the quick actions should be unchanged. The following steps help to verify this:

  1. With the GDK running, navigate to the Project > Issues screen for any project
  2. Select or create an issue
  3. Attempt to set the parent using the /set_parent quick action to an epic and incident
  4. Observe that the action succeeds for the epic, and fails for the incident, since this child / parent combination is not allowed
  5. Similarly, on the same issue, attempt to set a child using the /add_child quick action to another issue and a task
  6. Observe the issue fails, and the task succeeds for the same reasons as above

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 #568269 (closed)

Edited by Matt D'Angelo

Merge request reports