USHIFT-6792: Exclude unfinished runs to prevent previous failure masking

[ggiguash]

fetch_latest_per_job now excludes unfinished runs so that in-progress jobs don't mask their previous failures.

Chores: set story points to 0 when creating JIRA bugs.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-6792 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

fetch_latest_per_job now excludes unfinished runs so that in-progress jobs don't mask their previous failures.

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 openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1defa428-79ca-481d-bdd7-8d8eafcd14e0

📥 Commits

Reviewing files that changed from the base of the PR and between e1beadb and 95834b0.

📒 Files selected for processing (1)

• .claude/commands/analyze-ci/create-bugs.md

---

Walkthrough

The Prow-job script .claude/scripts/microshift-prow-jobs-for-release.sh now filters to records with a non-empty .finished field before grouping/selecting latest runs; the docs file .claude/commands/analyze-ci/create-bugs.md was updated to add customfield_10028: 0 (Story Points) to JIRA issue creation payloads.

Changes

Cohort / File(s)	Summary
Prow job filter .claude/scripts/microshift-prow-jobs-for-release.sh	Add filter to require .finished is present and non-empty prior to group_by(.job) and selecting latest run, altering which jobs and their finished/status/duration/url/build_id appear in output.
JIRA create-bugs docs .claude/commands/analyze-ci/create-bugs.md	Documentation change: include customfield_10028: 0 (Story Points) in additional_fields for created JIRA bug issues.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

✨ 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-robot]

@ggiguash: This pull request references USHIFT-6792 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

fetch_latest_per_job now excludes unfinished runs so that in-progress jobs don't mask their previous failures.

Chores: set story points to 0 when creating JIRA bugs.

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 openshift-eng/jira-lifecycle-plugin repository.

[ggiguash]

/verified by @ggiguash

[openshift-ci-robot]

@ggiguash: This PR has been marked as verified by @ggiguash.

Details

In response to this:

/verified by @ggiguash

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 openshift-eng/jira-lifecycle-plugin repository.

[pacevedom]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pacevedom

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:

• OWNERS [ggiguash,pacevedom]

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

[openshift-ci]

@ggiguash: 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.