[jira/grooming] add sprint filter and support no time range to grooming command #88
+24
−8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bryan-cox, jiajliu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
jiajliu
changed the title
| - **`/jira:create` `<type> [project-key] <summary> [--component <name>] [--version <version>] [--parent <key>]`** - Create Jira issues (story, epic, feature, task, bug) with proper formatting | ||
| - **`/jira:generate-test-plan` `[JIRA issue key] [GitHub PR URLs]`** - Generate test steps for a JIRA issue | ||
| - **`/jira:grooming` `[project-filter] [time-period] [--component component-name] [--label label-name]`** - Analyze new bugs and cards added over a time period and generate grooming meeting agenda | ||
| - **`/jira:grooming` `[project-filter] [time-period] [--component component-name] [--label label-name] [--sprint sprint-name]`** - Analyze new bugs and cards added over a time period and generate grooming meeting agenda |
Contributor
There was a problem hiding this comment.
IMHO, the sprint name also represents a time range, so I think we can merge it with the time-period field.
Contributor
There was a problem hiding this comment.
E.g
/jira:grooming OCPSTRAT "OTA 277" --component "Control Plane" --label "performance"
Author
There was a problem hiding this comment.
Good to know that a string name could be provided in time-period field, but according to my local testing, they returned different results.
/jira:grooming OCPBUGS "" --component "Cluster Version Operator" --sprint "OTA 277"
It retrieves and returns the bugs(such as OCPBUGS-61872 and OCPBUGS-54151), which is consistent with jira’s Sprint "OTA 277".
...
- OCPBUGS-61872: https://issues.redhat.com/browse/OCPBUGS-61872
- OCPBUGS-54151: https://issues.redhat.com/browse/OCPBUGS-54151
- CI Logs: Available in issue OCPBUGS-61872 additional info section
● ---
The grooming agenda has been generated successfully for sprint OTA 277 with the Cluster Version Operator
component in the OCPBUGS project. The sprint shows excellent completion with both bugs resolved:
...
/jira:grooming OCPBUGS "OTA 277" --component "Cluster Version Operator"
It retrieves a time range (September 16 - October 6, 2025) according to provided string "OTA 277." Then, it will identify and return bugs(such as OCPBUGS-62416 and OCPBUGS-61872), that were created during this period but are not consistent with jira's Sprint "OTA 277".
...
Summary: During the OTA 277 sprint (Sept 16 - Oct 6, 2025), only 2 new bugs were created for the Cluster
Version Operator component, and both have already been verified and closed. This indicates excellent sprint
execution with 100% completion rate.
The agenda includes:
- Detailed analysis of both issues (OCPBUGS-61872 and OCPBUGS-62416)
...
From the QE side, what we need is the result returned from the first example. It can help us plan and participate in sprint work effectively.
Contributor
There was a problem hiding this comment.
IIUC, this would require changes to the implementation to support it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
The grooming command is helpful for QE grooming tasks. This pull request adds support for
sprintfilter, enabling list generation based on sprint names. Additionally, the time-period argument can now be left empty, allowing for an unlimited time range.Checklist: