Previously set alert condition not displaying on metrics dashboard

Summary

In a project where an alert condition had been previously set, we can no longer see the alert condition on the metrics dashboard. Since we can no longer see or access the alert condition, we cannot edit it or delete it.

Screen_Shot_2019-07-25_at_2.30.17_PM

We can see that the alert still exists because the alert violation is still triggering issues to be created.

Screen_Shot_2019-07-25_at_2.29.58_PM

When we try to create a new alert for the same metric, we get an error.

alert-set-bug

Steps to reproduce

You must be a maintainer to set alert conditions

  1. Visit the project where we're seeing this issue at https://gitlab.com/jivanvl/test-node-project/environments/711946/metrics
  2. Observe that the "alert" icon for the "Core Usage (Pod Average)" metric indicates that there are no alerts set.
  3. Navigate to the issues page at https://gitlab.com/jivanvl/test-node-project/issues?sort=created_date
  4. Observe that there are still issues being created by alerts set on "Core Usage (Pod Average)"

Example Project

https://gitlab.com/jivanvl/test-node-project/environments/711946/metrics

What is the current bug behavior?

We can not see any alert condition set for "Core Usage (Pod Average)" on the metrics dashboard page.

What is the expected correct behavior?

We should see the alert condition on the metric "Core Usage (Pod Average)" and should be able to edit or delete it.

Output of checks

This bug happens on GitLab.com

cc/ @sarahwaldner