Issue was discovered in an MR

Issue was discovered on gitlab.com environment.

Issue was discovered on dev.gitlab.org.

Issue was discovered from canary.staging.gitlab.com environment.

Issue was discovered on canary.gitlab.com.

Issue was discovered by the end-to-end test suite

Issues related to creating, maintaining and deleting forks

Follow up issues that are created from merge requests

The test fails from time to time due to infrastructure issues.

The DOM selector used in the test is unreliable.

Test is failing due to a legitimate transient bug

Test data state leaked through test cases. See https://docs.gitlab.com/ee/development/testing_guide/flaky_tests.html#state-leak

The test use random values, that sometimes match the expectations, and sometimes not.

The test is assuming a specific date or time.

The test assumes the dataset is in a particular (usually limited) state, which might not be true depending on when the test run during the test suite.

Unhealthy test issues with less than 4 flakiness reports.

Unhealthy test issues with between 4 and 21 flakiness reports.

Unhealthy test issues with between 22 and 41 flakiness reports.

Unhealthy test issues with 42 or more flakiness reports.

centralized IPS/IDS program for DoD/Allies coordinated by DISA, 37+ OEMs in the Joint Regional Security Stack. So big and awkwardly implemented it's drawn formal Pentagon criticism in 2017 and 2018. Multi-billion dollar IPS/IDS.