Threat Monitoring Policy Page Design Bug - New rule does not auto-populate on load
Summary
The Threat Management Policy page does not load with a new rule pre-populated in the UI
Steps to reproduce
- Visit https://gitlab.com/gitlab-org/threat-management/defend/demos/network-policy-demo/-/threat_monitoring/policies/new
- Note that a new rule is not pre-populated in the UI
Example Project
What is the current bug behavior?
Currently a new rule is not pre-populated:
What is the expected correct behavior?
The correct behavior is for a new rule to be pre-populated when the page is first loaded:
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
-
frontend add an initial rule for a non-existing policy in policy-editor
Edited by Alexander Turinske