Potential GitLab bug: Merging a MR caused a second (but inverse) MR to automatically merge

Here’s the situation…
My team had multiple Merge Requests on a project. One developer decided to use gitlab to merge develop back into their feature branch. When the branch was merged, their existing Draft Merge Request was also merged by gitlab.

Draft Status Merge Request: feature_branch->develop

New Merge Request: develop->feature_branch

The user used gitlab to create the second merge request, resolved merge issues on gitlab, then clicked the merge button on gitlab. Then we realized that their draft status merge request was also merged in the process. This is obviously undesired behavior.

Has anyone experienced a similar issue?

Self hosted GitLab Community Edition 15.1