Labels
Prioritized labels 0
Drag to reorder prioritized labels and change their relative priority.
Labels 3,644
-
corpsec-priorityops-lowGitLab.comCorporate Security Priority. Low priority (same/next week) day-to-day requests.
-
corpsec-priorityp0GitLab.comCorporate Security Priority. Project fire drill (crisis, incident, urgent deadline).
-
corpsec-priorityp1GitLab.comCorporate Security Priority. Project/task in the next few weeks or sprints.
-
corpsec-priorityresearchGitLab.comCorporate Security Priority. Non-priority research and discovery.
-
corpsec-prioritywishlistGitLab.comCorporate Security Priority. Project on the uncommitted wishlist.
-
corpsec-research-miscGitLab.com / GitLab Security DivisionUsed for issues involving research that is done by CorpSec but not under or aligned to a specific team within or outside of CorpSec
-
corpsec-statusbacklogGitLab.comCorporate Security Status. This issue is in our backlog to be completed within a year (see priority).
-
corpsec-statusblockedGitLab.comCorporate Security Status. This issue has started but is blocked for a technical reason. Blocked issues get attention of engineers.
-
corpsec-statusinboxGitLab.comCorporate Security Status. This issue is new and has not been evaluated yet.
-
corpsec-statusreviewGitLab.comCorporate Security Status. The work is mostly complete and is waiting on final review or cleanup work.
-
corpsec-statusscheduledGitLab.comCorporate Security Status. This issue has been scheduled to be worked on in an upcoming iteration milestone.
-
corpsec-statuswaitingGitLab.comCorporate Security Status. This issue has started but is on hold waiting for a business reason or review. Waiting issues get attention of managers.
-
corpsec-statuswipGitLab.comCorporate Security Status. This issue is a work in progress. The team member will assign this status when they pick it up.
-
corpsec-statuswishlistGitLab.comCorporate Security Status. For any issues not being worked on in the next year or become dormant. Closed issues can be reopened if priority changes.