In the general settings area (\"Administration\" - \"Settings\" - \"Custom Properties\"), it is possible to activate/deactivate the plugin in general.\nFurthermore, it is also possible to control whether configurations are permitted at namespace level.\nTo do this, click on the button to edit the respective setting.\nThis navigates the user to a subpage where the setting can be configured.
\nTo assist the user in creating custom properties, it is possible to create predefined keys.\nTo create a new key, the 'Predefine Custom Property' button must be clicked.\nThis navigates the user to a new subpage.\nHere, the user can define a new key in a text input field.\nThe same validation rules apply to predefined keys as when creating a custom property (see documentation for overview).
\nAdditionally, the user can use a chip input to define a set of values, which are allowed to\nbe used for the custom properties with the corresponding key.\nNew values have to be entered in the input field and then be confirmed by pressing the enter key.\nExisting values can be removed by pressing the small \"x\" symbol for the value.\nProperties already set for repositories will not be validated subsequently, when the configuration is changed.
\nFurthermore, the user can use a radio input to specify a type for the custom property.\nThere are four options for this:\nA plain property, a default property, a mandatory property and a multiple choice property.
\nFor mandatory properties, it is required that each repository has a custom property with the respective key and a value.
\nFor default properties, a default value is implicitly assumed if the respective custom property has not yet been defined for a repository.\nIf default property is specified as the type, the user must also specify a default value.\nIf the values for the custom property are unrestricted (i.e. if no permitted values are set),\nthe default value is entered using a text input.\nIf permitted values are specified, a drop-down menu with all permitted values and an empty input field is available as options.
\nWith multiple choice properties, it is possible to select more than one value for that custom property.\nBut for this type, it is required to define allowed values.
\nFor plain properties no further rules will be applied.
\nThe predefined keys can also be edited and deleted using the respective action buttons in the key overview.\nThe key overview also shows whether a multiple choice, default or mandatory value has been defined for the respective custom property.\nIf the custom property has a mandatory value, icons are used to indicate whether all repositories have defined this mandatory property.\nIf at least one repository is missing, the user receives a warning icon as feedback.\nThis icon can be clicked to obtain an overview of all repositories for which the mandatory value still needs to be defined.
\nAdditional keys can be defined at the namespace level.\nThese are only suggested for repositories of the respective namespace.\nThe creation, editing and deletion of keys is analogous to the global configuration.\nIn addition, globally defined keys are also listed in the key overview and marked with the tag 'Global Template'.\nThese cannot be edited at the namespace level.
\n