Labels

Issue has gone through Quad Planning process (PM,Dev,UX,QE) and has recommendations from Quality Engineering

Issue has gone through Quad Planning process (PM,Dev,UX,QE) and does not require any additional action

Issue requires SET review per our Quad Planning process (PM/Dev,UX,QE)

This test is failing because of a change to the test code or framework

This test is failing due to an actual bug in the application

This test fails intermittently

This test is a :flaky test but it might be blocking other MRs and so should be quarantined while it's under investigation

This test is outdated due to a feature change in the application and must be updated to fit the new changes

This test is failing due to problems with the test environment and will not be fixed within 24 hours

This test is quarantined temporarily due to an issue or MR that is a prerequisite for this test to pass

Issues related to quick actions: https://docs.gitlab.com/ee/user/project/quick_actions.html

Issues that are straightforward for community contributors and have implementation plans. See criteria for quick win issues: https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#criteria-for-quick-win-issues

Quick win issues that are ideal for first-time community contributors to work on

Issues and Merge Requests generally related to Rails

Issues and Merge Requests related to upgrading to Rails 5

Issues and Merge Requests related to upgrading to Rails 5.1

Issues and Merge Requests related to upgrading to Rails 5.2