69 labels
Sort
Sort
-
Bug
Used in discussion about a bug in comments or commits -
CVE-2023-5764
Denotes items related to the CVE -
CodeReview
Used in comments (issues/MR/commits) to denote code review related items -
Documentation
Documentation items -
Feature
Used in discussion about a Feature in comments or commits -
Lint
Used in comments (issues/MR/commits) to denote lint tasks todo, done, fixed -
Privacy
Used in comments (issues/MR/commits) to denote privacy related items -
Security
Used in comments (issues/MR/commits) to denote Security related items -
breaking-change
label used to denote that the issue/Merge Request does/will introduce a breaking change -
bug::reproducable
Given to an issue when the bug has been confirmed as re-producable. Can also be used in comments and commits. -
bug::unable to reproduce
Given to an issue when the bug that is not able to be reproduced. Can also be used in comments and commits. -
code review::complete
-
code review::not started
-
code review::rejected
-
code review::underway
-
difficulty::Full Development
Level 3. Difficulty representing that the task to complete must be planned and created. -
difficulty::Good First Issue
Level 1. Difficulty representing that the task is very simple and with limited knowledge can be completed. -
difficulty::Prior Knowledge
Level 2. Difficulty representing that the task requires some prior knowledge of either the technology or the project for task completion. -
documentation::complete
Issues, Merge Requests -
documentation::no change required
Issues, Merge Requests and used to denote no documentation changes required -
documentation::not started
Issues, Merge Requests -
documentation::stalled
Issues, Merge Requests -
documentation::underway
Issues, Merge Requests -
impact::0
-
impact::1
-
impact::2
-
impact::3
-
impact::4
-
impact::5
-
ops::ansible-roles
OPS project tag -
ops::automation
-
ops::gitlab-ci
OPS project tag -
ops::marcas
OPS project tag -
ops::python-gitlab-management
OPS project tag -
ops::website
-
priority::0
-
priority::1
-
priority::2
-
priority::3
-
priority::4
-
priority::5
-
stage::Ready for Development
-
stage::develop
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits -
stage::feedback required
-
stage::planning
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits -
stage::test
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits -
stale
Label given to issues/merge requests that are considered stale due to no collaboration and is a mark for closure. -
triage
Tag given to issues/merge requests requiring triaging by the team. -
triage::not_confidential
This tag is given by the triage bot so that URLs can be added to an issue/comment. A triage policy for NFC wide should remove this label. -
type::CI / CD
-
type::automation
This type is used to denote an automation job -
type::bug
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits -
type::compliance
-
type::discussion
Type for Issues. Can also be used in discussion in comments. -
type::documentation
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits -
type::feature
type for Issues and Merge Requests. Can also be used in discussion in comments and commits -
type::invalid
label given to tickets that require no action or are deem as invalid. -
type::quality assurance
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits -
type::question
Type for Issues. Can also be used in discussion in comments. -
type::security
Type for Issues and Merge Requests. -
type::specification
Design specification -
workflow::complete
Issues, Merge Requests -
workflow::not ready
-
workflow::not ready::blocked
-
workflow::not started
Issues, Merge Requests -
workflow::ready to commence
Issues, Merge Requests -
workflow::stalled
Label given to issues/merge requests where no work has occured in x days iaw triage policy. -
workflow::underway
Issues, Merge Requests -
workflow::underway::develop