95 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 -
v1.0.0
Version that is affected -
v1.0.1
Version that is affected -
v1.1.0
Version that is affected -
v1.1.1
Version that is affected -
v1.1.2
Version that is affected -
v1.10.0
Version that is affected -
v1.10.1
Version that is affected -
v1.10.2
Version that is affected -
v1.10.3
Version that is affected -
v1.11.0
Version that is affected -
v1.12.0
Version that is affected -
v1.13.0
Version that is affected -
v1.13.1
Version that is affected -
v1.13.2
Version that is affected -
v1.2.0
Version that is affected -
v1.3.0
Version that is affected -
v1.4.0
Version that is affected -
v1.5.0
Version that is affected -
v1.6.0
Version that is affected -
v1.7.0
Version that is affected -
v1.7.1
Version that is affected -
v1.7.2
Version that is affected -
v1.8.0
Version that is affected -
v1.8.1-a1
Version that is affected -
v1.8.1-a2
Version that is affected -
v1.9.0
Version that is affected -
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
-
Organization level labels that can be used with all repositories under this organization
-
Area/CI-CD
Documentation changes -
Area/Documentation
Documentation changes -
Area/Security
This is security issue -
Area/Testing
Issue or pull request related to testing -
BugFailure to Confirm
Bug exists due to not confirming/testing code -
BugRegression
THe bug is a regression of a feature -
BugTo be Confirmed
This bug is not confirmed -
BugUnable to Reproduce
A developer can not re-create/re-produce the bug -
Compat/Breaking
Breaking change that won't be backward compatible -
ImpactCritical1
The impact is critical in that it is blocking or prevents usage. -
ImpactHigh2
The impact requires that changes be made for continuted usage. -
ImpactLow4
The impact requires the user approach from a different angle for continued usage. -
ImpactMedium3
The impact requires a workaround for continued usage. -
ImpactVery Low5
The impact has a slight effect on usage. -
PriorityHigh2
The priority is high -
PriorityLow4
The priority is low -
PriorityMedium3
The priority is medium -
PriorityVery High1
The priority is critical -
PriorityVery Low5
The priority is very low -
ReviewedConfirmed1
Issue has been confirmed -
ReviewedDuplicate2
This issue or pull request already exists -
ReviewedInvalid3
Invalid issue -
ReviewedWon't Fix3
This issue won't be fixed -
StatusAbandoned3
Somebody has started to work on this but abandoned work -
StatusBlocked1
Something is blocking this issue or pull request -
StatusNeed More Info2
Feedback is required to reproduce issue or to continue work -
TypeBug
Something is not working -
TypeEpic
Epic User Story -
TypeFeature
Feature / Module -
TypeIncident
Something occured related to a service -
TypeRFE
Request for Enhancement -
TypeTask
A work item that must be done -
UrgencyLow4
Prioritize this amoungst your list of things to do. -
UrgencyMajor1
Urgency is so high it should have been dealt with last week. -
UrgencyMedium3
Start as soon as possible. -
UrgencyVery High2
Urgency is high enough to warrant near immediate commencement. -
UrgencyVery Low5
Add this to your list of things to do.