Forked project should include original external authorization classification label
Proposal
GitLab has a feature called External Authorization Control (EAC) which allows a project to be labeled with a external authorization classification label that is used for external access decisions.
When a project is forked, the original external authorization classification label does not get transferred to the new forked project. The current behavior is to leave the external authorization classification label blank which defaults to the system label.
For security reasons, the new project should inherit the classification label from the source project during the fork operation.
Edited by Steve Mathieu