outcome-rater

You can triage Jira Outcome tickets by evaluating them against press-release worthiness, leadership priority fit, bucket detection, and CY26/27 relevance to generate keep, close, or clarify recommendations for each item.

Evaluating if a Jira ticket should be closed involves applying quality gates like press-release worthiness and leadership priority fit. This structured decision support approach replaces subjective reviews with actionable keep, close, or rewrite verdicts.

Yes, you can fetch Jira tickets directly for prioritized review by providing your Jira base URL and a Personal Access Token (PAT). The system then automatically retrieves Outcome tickets to apply the four-gate triage evaluation.

Yes, Jira triage supports multi-source ticket intake including pasted text, uploaded exported Jira PDFs, and direct Jira fetching. This flexibility allows you to process Outcome tickets from various export formats.

Automated quality gates for Jira ticket triage require clear Outcome descriptions to function effectively. If tickets are poorly written, the system may suggest splitting work into discrete outcomes or rewriting to clarify the outcome rather than providing a direct keep or close verdict.

To generate a markdown report after rating Jira Outcomes, the system extracts key fields from the evaluated tickets and writes the structured keep, close, and clarify recommendations into a dated markdown output file.