Committing draft versions of objects to Git repository should be supported

Current Situation

When committing a folder to a Git repository by using the "Store to Git Repository" operation, it is possible to select "Draft" and "Deployed". When both versions do exist then the deployed version is stored to the Git repository.

Desired Behavior

• The checkboxes have to be rearranged to signal the priorization of objects.
  • The first row gets the label "Deployed / Released" instead of "Filter" and one checkbox only
    • Default - checked
  • The second row has a rowlabel and two checkboxes, a "Draft" checkbox and a "Valid Only" checkbox
    • Default - unchecked 
    • the rowlabel is initially or per default empty
  • The row label of the second row
    • is set to "add draft version if no deployed version exists" in case both - "Deployed/Released" and "Draft" is checked
    • is empty if only one of "Deployed/Released" and "Draft" is checked
• add tooltip with a priority description
  • text
    "Per default storage of deployed/released versions is preferentially supported.
    Choosing both draft and deployed/released versions will result in drafts being stored only, if no deployed/released version exists.
    Choosing only draft versions will result in draft version being stored even if deployed/released versions exist.
    Draft versions are considered untested and therefore unsafe."
• UI behavior
  • use case:  "Deployed / Released" is already checked and user checks "Draft" checkbox
    • the second rows label changes to "add draft version if no deployed version exists"
    • the "valid only" checkbox will be set automatically
  • uses case: user unchecks "Deployed / Released" checkbox
    • A:  "Draft" checkbox is not checked
      • check "Draft" checkbox automatically
      • check "Valid Only" checkbox automatically
      • make "Draft" checkbox uneditable
      • the row label stays empty
    • B: "Draft" checkbox is already checked
      • only make "Draft" checkbox uneditable
  • use case: user checks "Deployed / Released" checkbox
    • make "Draft" checkbox editable again

Maintainer Note

The JS7 JOC Cockpit repository APIs as well as the GUI are not designed as a fully supported Git feature, but a rollout support feature.

The issue occurs, as mentioned above, only when the software has to prioritize between draft and already deployed versions as both checkboxes are selected.

As the feature is designed to support a rollout process between dev -> test and test -> prod the already deployed and therefore presumably tested versions are prioritized. This is functionally different from the deployment of objects that prioritizes draft objects.