feat(quay): add dependent_bug_target_versions to quay and quay-operator

[jbpratt]

Enables automatic JIRA clone creation during backports.

Summary by CodeRabbit

This PR updates the JIRA lifecycle plugin configuration to enable automatic JIRA bug clone creation during backports for the Quay and Quay Operator repositories.

What changed:
The configuration file core-services/jira-lifecycle-plugin/config.yaml now includes dependent_bug_target_versions mappings for both quay and quay-operator repositories across their supported release branches (redhat-3.10 through redhat-3.18).

Practical impact:

• When bugs are backported to older branches of Quay or Quay Operator, JIRA will automatically create dependent bug clones in the specified target versions
• Each branch configuration specifies which future versions should automatically receive dependent bugs (e.g., fixes to the redhat-3.10 branch will automatically create dependent bugs for redhat-3.11, quay-v3.11.z, etc.)
• This streamlines the backport process by eliminating manual JIRA ticket creation for dependent versions

Lines changed: 36 additions (configuration entries only)

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@jbpratt: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 6b1092cf-d40d-40f6-80f4-69a503fa926f

📥 Commits

Reviewing files that changed from the base of the PR and between 07efae4 and c7d32cb.

📒 Files selected for processing (1)

• core-services/jira-lifecycle-plugin/config.yaml

---

Walkthrough

This pull request adds dependent_bug_target_versions configuration lists to existing branch entries in a JIRA lifecycle plugin configuration file. The same dependency versioning pattern is applied to both the quay and quay-operator repositories across their Red Hat release branches (3.10 through 3.18), specifying target versions that dependent bugs should track.

Changes

Dependent bug target versions configuration

Layer / File(s)	Summary
Dependent bug target versions for quay and quay-operator core-services/jira-lifecycle-plugin/config.yaml	Adds dependent_bug_target_versions configuration to quay (redhat-3.10 through redhat-3.18) and quay-operator (redhat-3.10 through redhat-3.18) repository branch entries, specifying next version targets as dependent targets while preserving existing target_version and validate_by_default settings.

---

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding dependent_bug_target_versions configuration to quay and quay-operator repos.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PR modifies only YAML configuration files; no Ginkgo test code or test names are present or modified in this PR.
Test Structure And Quality	✅ Passed	PR contains config.yaml changes, not Ginkgo test code. Repository uses standard Go testing package, not Ginkgo framework. Custom check inapplicable.
Microshift Test Compatibility	✅ Passed	This PR only modifies JIRA configuration YAML files and does not add any Ginkgo e2e tests, making the MicroShift test compatibility check not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR contains no Ginkgo e2e tests; it only modifies JIRA lifecycle plugin YAML configuration. The SNO test compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only JIRA lifecycle plugin config.yaml (release management config), not deployment manifests or operator code. Topology-aware scheduling check is not applicable.
Ote Binary Stdout Contract	✅ Passed	PR contains no process-level code modifications to OTE binaries. Shell script additions are CI setup steps, not OTE binaries subject to the JSON stdout contract.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This PR adds only configuration YAML files to the JIRA lifecycle plugin; no Ginkgo e2e tests are added, so the IPv6/disconnected network compatibility check does not apply.
No-Weak-Crypto	✅ Passed	PR only modifies a YAML configuration file with version and metadata entries; no weak crypto, custom implementations, or insecure comparisons introduced.
Container-Privileges	✅ Passed	PR modifies only JIRA lifecycle config (version strings), not K8s manifests or container specs. No privileged settings found.
No-Sensitive-Data-In-Logs	✅ Passed	Configuration file contains only version numbers, branch names, and JIRA workflow settings; no passwords, tokens, API keys, PII, or sensitive data that could be exposed in logging.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bradmwilliams, jbpratt

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• core-services/jira-lifecycle-plugin/OWNERS [bradmwilliams]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@jbpratt: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci]

@jbpratt: Updated the jira-lifecycle-plugin-config configmap in namespace ci at cluster app.ci using the following files:

• key config.yaml using file core-services/jira-lifecycle-plugin/config.yaml

Details

In response to this:

Enables automatic JIRA clone creation during backports.

Summary by CodeRabbit

This PR updates the JIRA lifecycle plugin configuration to enable automatic JIRA bug clone creation during backports for the Quay and Quay Operator repositories.

What changed:
The configuration file core-services/jira-lifecycle-plugin/config.yaml now includes dependent_bug_target_versions mappings for both quay and quay-operator repositories across their supported release branches (redhat-3.10 through redhat-3.18).

Practical impact:

• When bugs are backported to older branches of Quay or Quay Operator, JIRA will automatically create dependent bug clones in the specified target versions
• Each branch configuration specifies which future versions should automatically receive dependent bugs (e.g., fixes to the redhat-3.10 branch will automatically create dependent bugs for redhat-3.11, quay-v3.11.z, etc.)
• This streamlines the backport process by eliminating manual JIRA ticket creation for dependent versions

Lines changed: 36 additions (configuration entries only)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.