Project Confidentiality Class
Proposal
In GitLab, classification is made possible for visibility and accessibility; ie: we are able to globally set visibility and access controls. It also gives us the ability to classify/label issues, groups or merge requests within a project.
What Gitlab doesn't do is give us the ability classify the confidentiality of the project itself for the information within the project.
Feature Request:
Description: We should be able to classify the confidentiality level of the content of a project.
Requirements:
-
'Confidentiality-Class' field is added to project creation
-
Only the Maintainer/Owner should be authorized to set or change the classification (editable) -
It should be globally configurable (mandatory for project creation or not) -
The field should be set as a drop down -
We should be able to set a default confidentiality-class (default for new project: Confidential) -
Admins should be able to pre-populate with required values We should be able to define the default value as needed (For new projects, this field will be setup as a mandatory & for existing projects, we will define the default Confidentiality class to 'Confidential' for example) -
Changes to the confidentiality class should be auditable (see in the logs when the confidentiality field was changed from X to Y and by whom?) -
This classification-class should be visible. When we browse to the project, we should be able to view the classification
- Confidential Class on clone:
-
Confidentiality class visible in the output of the clone command -
When somebody clones a project folder, the attribute should be cloned too with its existing value. -
This means it is visible but also editable for further actions if needed**
Edited by Brian Collins


