When processing MRs, only those opened should be considered
During the last executions of chatops run release merge --security --master
our tooling failed to recognize https://gitlab.com/gitlab-org/security/gitlab/-/issues/306 and https://gitlab.com/gitlab-org/security/gitlab/-/issues/312 as "Ready to be processed":
- https://gitlab.com/gitlab-org/security/gitlab/-/issues/306 - In theory, this one is ready to be processed (it has 4 MR's associated one for master and 3 backports all of them assigned to the bot), but it has associated one merged MR from GitLab Pages https://gitlab.com/gitlab-org/security/gitlab-pages/-/merge_requests/6 that is not assigned to the bot (it's fine for this one not to be assigned to the bot since GitLab-Pages security release is handled independently of the GitLab security release)
- https://gitlab.com/gitlab-org/security/gitlab/-/issues/312 - This one is also ready to be processed (it has all MRs required (one for master and 3 for backports, all of them assigned to the bot), but it has one security workhorse MR that is opened and not assigned to the bot https://gitlab.com/gitlab-org/security/gitlab-workhorse/-/merge_requests/17.
Proposal
When analyzing which security issues are ready to be processed, only considered MRs associated with the same project as the issue and MRs that are opened.
Edited by Mayra Cabrera