Skip to content

Add scan.py to offload triage Jira scan from MCP to REST API #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adalton merged 15 commits into from
Aug 27, 2026
Merged

Add scan.py to offload triage Jira scan from MCP to REST API #79

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
15 commits
Select commit Hold shift + click to select a range
2a7a200
Add scan.py to offload triage Jira scan from MCP to REST API
adalton Jul 16, 2026
23d7295
Address CodeRabbit review feedback on scan.py
adalton Jul 16, 2026
8137a98
Reject userinfo and fragments in JIRA_URL validation
adalton Jul 16, 2026
9054a39
Clarify AI_WORKFLOWS_ROOT resolution wording in scan.md
adalton Jul 16, 2026
a75d997
Merge main into andalton/triage-scan-jira-pagination-normalization
adalton Jul 16, 2026
6197d73
Remove duplicate zero-results guidance from scan.md
adalton Jul 16, 2026
646a79f
Merge main into andalton/triage-scan-jira-pagination-normalization
adalton Jul 22, 2026
2e782da
Merge remote-tracking branch 'origin/main' into andalton/triage-scan-…
adalton Aug 26, 2026
f6ded2c
Address CodeRabbit outside-diff findings on scan.py
adalton Aug 26, 2026
4cedc38
Cancel superseded test runs with a concurrency group
adalton Aug 26, 2026
3519a6b
Convert malformed-URL ValueError to ScanError in validate_jira_url
adalton Aug 26, 2026
faaa230
Merge remote-tracking branch 'origin/main' into andalton/triage-scan-…
adalton Aug 26, 2026
997c3e4
Reconcile triage version to 0.5.0 after merging main (#78)
adalton Aug 26, 2026
7b72010
Address Amir's review: pagination, null fields, negative window
adalton Aug 26, 2026
f0fb85e
Harden issue-key handling and clarify read-only limit (CodeRabbit)
adalton Aug 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion triage/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,12 @@ graph TD

## Prerequisites

- **Jira MCP server** — the `user-mcp-jira` MCP server must be configured and authenticated
- **Jira access** — the authenticated user must have read access to the target project
- **Jira MCP server** — the `user-mcp-jira` MCP server must be configured and authenticated (used by `/start` and `/assess`)
- **Environment variables for `/scan` (and `/run`, which includes scan)** — the scan phase calls the Jira REST API directly via `scripts/scan.py` instead of MCP:
- `JIRA_URL` — Jira instance base URL (e.g., `https://redhat.atlassian.net`)
- `JIRA_TOKEN` — API token or Personal Access Token
- `JIRA_EMAIL` — (optional) account email; set this when using an API token (Basic auth); omit for PATs (Bearer auth)

## Phases

Expand Down
2 changes: 1 addition & 1 deletion triage/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: triage
version: 0.4.0
version: 0.5.0
description: >-
Bulk-triage unresolved Jira bugs with AI-driven recommendations and an
interactive HTML report. Scan also loads recently resolved bugs for regression
Expand Down
4 changes: 2 additions & 2 deletions triage/guidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,15 +34,15 @@ artifacts and published output from this workflow.
- **No Jira writes** — this workflow must not create, update, close, or comment on any Jira issue
- **No fabricated data** — if a field is missing from the Jira response, report it as missing; never invent values
- **No skipping issues** — every unresolved bug in the scan results must appear in the analysis and report
- **Read-only MCP tools only** — each phase declares its allowed tools; never call a tool outside that list. No phase may use write-oriented Jira tools (`jira_create_issue`, `jira_update_issue`, `jira_delete_issue`, `jira_transition_issue`, `jira_add_comment`, `jira_add_worklog`, `jira_create_issue_link`, etc.)
- **Read-only Jira access only** — each phase declares its allowed tools; never call a tool outside that list. The read-only restriction covers both Jira MCP tools and the approved `scripts/scan.py` REST client, which issues only `GET /rest/api/3/search/jql`. No phase may use write-oriented Jira tools (`jira_create_issue`, `jira_update_issue`, `jira_delete_issue`, `jira_transition_issue`, `jira_add_comment`, `jira_add_worklog`, `jira_create_issue_link`, etc.)

## Allowed Tools Per Phase

| Phase | Jira MCP tools (read-only) | Local tools |
|---------|-------------------------------------|--------------------------------|
| Run | Per phase below | Per phase below |
| Start | `jira_search` | `mkdir` (create artifact dir) |
| Scan | `jira_search` | Write `issues.json` and `resolved.json` |
| Scan | none (script calls REST API directly) | Run `scripts/scan.py`; read stdout/stderr |
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Resolved
| Analyze | none | Read `issues.json`, read `resolved.json` (if present), write `analyzed.json` |
| Report | none | Read `analyzed.json`, read/update `issues.json` (renderer reads `jiraBaseUrl` from it); run `render_report.py`; write `ai-synthesis.json`, `report.html` |
| Assess (`/assess`) | `jira_search` | Optionally read `issues.json`; no required artifact writes |
Expand Down
Loading
Loading