co-pilot-scripts

Scripts automating work created with copilot

Scripts

analyze_cbl_issue.py — Analyzes a single CI Bug Log (CBL) issue by querying the knownfailure database, showing bug title, last-seen date, and per-test/per-platform failure breakdown with external links.
analyze_kdec5_backlog.py — Fetches an assignee's open Jira bugs, runs CBL assessment on each, and produces a markdown report categorized by urgency.
backlog_query.py — Queries Jira for a given assignee's open backlog, gathers detail (comments, links), flags bugs for CBL assessment, and writes a per-user report.
backlog_team.py — Batch-runs backlog_query.py for every member of a hardcoded team list, collecting all individual backlog reports.
condense_done_issues.py — Replaces detailed analysis sections for completed issues in an assessment markdown report with a simple "DONE" marker.
patch_assessment_next_steps.py — Patches a specific assessment report by replacing all "(TBD) Next Steps" placeholders with predetermined actions for each Jira issue.
run_assessment.py — Fetches unassessed VLK Jira bugs via JQL presets, resolves them to CBL issue IDs, runs knownfailure-based analysis, and generates a dated markdown assessment report.
update_jira.py — CLI tool to update a Jira issue's labels, priority, exposure, assignee, and/or add a comment via the Jira REST API.

use co-pilot help to setup up access to jira via token
set up access to intenral and extenral CBL using R/O credentials from CI - ask other users or CI for them

After setting up CBL access and jira tokens simply ask co-pilot for:

do assessment of jiras from "jira query you want to use" not older than 4 days Script should fetch all jiras for given query not older than 4 days, gather all data for all of them and put it in separate report. You can specify location of such reports.
gather all jiras for "team member" in RANK order from backlog dashboad, assess those issues
assess VLK-XXXX and put it in 'given location'