It seems like everybody so far has been just overriding the bug checker on the openshift/etcd branches.

Currently it expects us to merge into master first to automatically get into the current release branch, which we don't make use of. Directly merging into the current release branch complains about a missing bug in the next higher version, which might not even be a label in JIRA yet and impossible to create.

We can create a custom config in:
https://github.com/openshift/release/blob/master/core-services/jira-lifecycle-plugin/config.yaml

We were told that "rook" at the bottom has a similar configuration:
> I think just adding a section for openshift/etcd/openshift-4.12 that sets the target_version and validate_by_default without dependents should be enough. See how red-hat-storage/rook did their configuration for release branches.

relevant slack thread: https://coreos.slack.com/archives/C027ZPSD133/p1662643175160519