Skip to content

Enforce one escalation policy per project

What does this MR do?

For the first iteration of Escalation Policies we are limiting to one policy per project. &4638

This adds this check which was not enforced before.

We cannot add a DB constraint as the migration was made already and therefore records may exist. This is not a problem as when processing we take the first record !62361 (comment 593948440).

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team

Related to #332433 (closed)

Edited by Sean Arnold

Merge request reports