Parsing error occurs when editing a newly created policy
Summary
- newly created policies have parsing errors when editing
Steps to reproduce
- Navigate to a project => Secure => Policies => New policy => Scan Result Policy => Create a policy in rule mode => Save it
- Navigate back to the project => Secure => Policies => Select the newly create policy => Edit policy
Example Project
What is the current bug behavior?
Rule mode is disabled when editing the newly created policy
What is the expected correct behavior?
Rule mode is disabled when editing the newly created policy
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
Edited by Alexander Turinske