Rhdh Test Plan Review

Never modify Jira tickets without explicit user approval. Collect all decisions first, summarize them, then ask whether to apply — direct update [d], comment [c], or discard [n].

Different platforms accumulate versions differently:

• OCP: accumulate all active versions
• AKS, EKS, GKE, Quay: single latest version only — replace, never accumulate
• ARO, OSD, ROSA: single version each, evaluated independently — replace if a newer version is GA before code_freeze
• RHBK: track major versions only (e.g., 26 not 26.0); accumulate all active majors
• PostgreSQL: RHDH support policy is the baseline; Backstage-only versions require a Jira Feature ticket warning

Add/remove decisions are based on code_freeze and ga_date from the RHDH schedule sheet — not today's date.

• Add: version GA date ≤ code_freeze
• Remove: version EOL date ≤ ga_date

Jira descriptions are ADF (nested JSON). When updating, modify only version strings and date cells inside existing table cells — never convert to plain text and back. Preserve all other ADF structure exactly.

Never read .jira-token into context. Always use shell substitution: "$(cat "$TOKEN_FILE")".

RHDH Test Plan Review

Provide a Jira ticket ID or URL (e.g., RHIDP-8994) to begin.

Wait for response before proceeding.

| Input | Workflow | |-------|----------| | Jira ticket ID or URL | Read workflows/review-test-plan.md and follow it |

| Reference | Purpose | Path | |-----------|---------|------| | sources | Lifecycle URLs and extraction guidance per platform/integration | references/sources.md | | google-sheets-setup | One-time gcloud auth setup for schedule sheet access | references/google-sheets-setup.md | | rhdh-jira auth | Jira REST API token setup and curl patterns | ../rhdh-jira/references/auth.md |

• [ ] RHDH version extracted from ticket
• [ ] Milestone dates fetched from schedule sheet
• [ ] All platform and integration versions checked against lifecycle sources
• [ ] Overview diff presented (key dates, platforms, integrations)
• [ ] Each proposed change reviewed interactively (a/k/e)
• [ ] User chose how to apply: [d] direct update, [c] comment, [n] discard
• [ ] If [d]: Jira description updated via REST API; child tasks offered one at a time
• [ ] If [c]: comment posted to ticket
• [ ] If [n]: confirmed no changes were made

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: redhat-developer
• Source: redhat-developer/rhdh-skill
• License: Apache-2.0

Install and usage instructions live in the source repository linked above.