Add escalation policy modal layout
What does this MR do?
Adds escalation policy modal layout with basic validation (name only)
This functionality is behind the feature flag
run
rails c
Feature.enable(:escalation_policies_mvc)Minimal license required is GitLab Premium
To check navigate to you project=>Operation=>Escalation Policies
The next step would be to add BE integration (request for schedules list, saving the escalation policy with the rules).
Initially, all was planned to be done in one MR but as the number of changes is already significant, I've decided to separate them at this stage. You should not expect any form interactions.
It is set as Draft as the base branch contains backend changes though not required for the current MR will be for upcoming MR. And as mentioned before I've planned initially to add the integration in scope of the current MR. Now to proceed with work based on this MR's changes and backend changes required for the integration this branch is based on backend branch which should be merged first
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
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 #268356 (closed)