Add /jira:query-qa-assignment command for QA coverage on Feature/Epic/QE story issue analysis

[gpei]

Summary

Adds a new Jira command to help teams identify QA coverage gaps across Features, Epics, and QE Stories for OpenShift releases. This command analyzes QA Contact assignments and provides comprehensive reports to ensure proper QA resource allocation.

Motivation

During release planning, it's critical to ensure all Features and Epics have QA Contacts assigned, and that all QE testing stories (pre-merge, e2e, CI implementation) have assignees. Manually tracking this across multiple projects, labels, and versions is time-consuming and error-prone. This command automates the entire process.

What This PR Does

• Adds /jira:query-qa-assignment command to the jira plugin
• Queries Features by label(s) and target version (e.g., CORS label, openshift-4.21)
• Checks QA Contact field on Features and Epics
• Finds QE testing stories and checks for assignees
• Generates detailed markdown reports with:
  • Summary statistics (total count, missing assignments, coverage %)
  • Lists of Features/Epics/Stories missing QA assignments
  • QA Contact distribution across the release
  • Breakdown by project, story type, and status
• Saves reports to .work/qa-reports/ directory

Command Features

• Multi-label support: Filter Features by one or more labels (e.g., CORS, SPLAT)
• Version-specific: Target specific OpenShift versions
• Project filtering: Optionally filter Epics by project(s)
• Hierarchical analysis: Features → Epics → Stories
• Comprehensive reporting: Coverage metrics, distribution statistics, and actionable insights

Usage Examples

# Single feature label
/jira:query-qa-assignment --feature-label CORS --target-version openshift-4.21

# Multiple feature labels
/jira:query-qa-assignment --feature-label CORS --feature-label SPLAT --target-version 4.21

# With epic project filter
/jira:query-qa-assignment --feature-label CORS --target-version 4.21 --epic-project CORS --epic-project SPLAT

Sample Output

QA Assignment Analysis Complete
================================

Query: Labels=[CORS], Version=openshift-4.21, Projects=[CORS]

Results:
  ✓ 19 Features analyzed
  ⚠️ 3 Features missing QA Contact
  ✓ 23 Epics analyzed
  ⚠️ 2 Epics missing QA Contact
  ✓ 60 QE Stories found
  ⚠️ 3 QE Stories missing Assignee

Coverage:
  Features: 84% have QA Contact
  Epics: 91% have QA Contact
  Stories: 95% have Assignee

Detailed report saved to:
  .work/qa-reports/qa-assignment-4.21-2025-10-31.md

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: gpei
Once this PR has been reviewed and has the lgtm label, please assign dgoodwin for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

Hi @gpei. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[stbenjam]

/ok-to-test