Merge Request Approval Rules Missing Rules
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
I have a project that has one approval rule defined via its project settings and two more (scan result) rules through a linked security policy. Now my understanding would be that when a new MR is created in this project, there should be three approval rules associated with the MR (my one project and two policy-based rules). However, the MR approval rule API endpoint only returns the two policy-based rules, the rule coming from the project settings is missing.
Within the UI, the rule is displayed correctly, telling me that the MR requires 1 approval from my project-specific rule. Also, attempting to merge the MR via the API results in an HTTP 405 error, as it should as long as not all required approvals are given. Now am I misunderstanding the concept of MR approval rules and my project-specific rule is not supposed to appear in the API response, or am I looking at an issue with the API? I'll be happy to provide more detailed information about the project, MR, rules etc., but wanted to ensure that it isn't intended behavior first.