Labels
Prioritized labels 20
Drag to reorder prioritized labels and change their relative priority.
-
congregateAzure DevOps Migration SupportGitLab.org / Professional Services Automation / Tools / Migration
-
congregateBitBucket Migration SupportGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregateCustomerGitLab.org / Professional Services Automation / Tools / Migration / CongregateIssues that are related to customer requests (feature of migration specific)
-
congregateDocsGitLab.org / Professional Services Automation / Tools / Migration / CongregateIssues involving documentation updates
-
congregateGitHub Migration SupportGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny issues related to support a GitHub/GHE migration to scale
-
congregateJenkins Variable Migration SupportGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregateLDAP migration supportGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny issue related to migrating LDAP configurations into GitLab
-
congregateNew FeatureGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny new feature or improvement for congregate
-
congregateGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregate::New FeatureconfigurationGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny new feature or improvement related to configuring congregate
-
congregate::New Featurelisting dataGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny new feature or improvement related to retrieving data from a source instance
-
congregate::New Featurestaging dataGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny new feature or improvement related to staging data for a migration
-
congregateSVN migration supportGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregateTFS SupportGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny issue related to supporting TFS to Git migrations
-
congregateTeamCity Variable Migration SupportGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregateTechnical DebtGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny issue created as a result of not addressing something during a fire-fight
-
congregateUI Refactor MVC 1GitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregatebugGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregatee2e-testGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregatesupportGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny issue created by a user of congregate looking for support from the congregate development team
Labels 3,621
-
automation:quick-win-removedGitLab.orgWhen the ~"quick win" label has been automatically removed because it doesn't meet the required criteria: https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#criteria-for-quick-win-issues
-
automation:reviewers-remindedGitLab.orgThis label keeps track of Community contribution MRs where assigned reviewers have been reminded to review the MR
-
automation:self-triage-encouragedGitLab.orgTrack wider community issues where the author has been encouraged to self triage
-
automation:stale-remindedGitLab.orgIdentifies issues / merge requests that have been nudged by the stale reminder
-
automation:top-flaky-testGitLab.orgLabel for issues created by automation for the tests that are identified as most flaky.
-
automation:top-flaky-test-fileGitLab.orglabel for issues automatically created for top flaky specs
-
availabilitylimitGitLab.orgGitLab, like most large applications, enforces limits within certain features. The absences of limits can impact security, performance, and availability. For this reason issues related to limits are considered as another category of ~"type::bug". https://about.gitlab.com/handbook/engineering/quality/issue-triage/#limit-related-bugs
-
awaiting feedbackGitLab.orgIssues that are blocked until more feedback is received from the reporter
-
backend completeGitLab.orgThe backend component of this piece of work has been completed, merged and verified.
-
backend-weight1GitLab.org(Trivial) The problem is very well understood, no extra investigation is required, the exact solution is already known and just needs to be implemented, no surprises are expected, and no coordination with other teams or people is required.
-
backend-weight2GitLab.org(Small) The problem is well understood and a solution is outlined, but a little bit of extra investigation will probably still be required to realize the solution.
-
backend-weight3GitLab.org(Medium) Features that are well understood and relatively straightforward. Bugs that are relatively poorly understood and may not yet have a suggested solution.
-
backend-weight4GitLab.org(Little more than Medium) Features that are well understood and slightly complex. Bugs that are loosely understood and without a suggested solution.