qa-ticket-report
Skill2 starsChanged 2 days agoMITView on GitHub
Post a QA test or retest result onto a Jira ticket in the team format. The header block is Test Result / Test Environment (<env> - Version <actual>) / Platform / Test Date / Test Data / Actual Result. A ticket with more than one case gets a `Test Case | Actual Result | Expected Result` table. Under that the comment explains what happened, with the screenshots inline in the comment, not as an attachment list. Use WHENEVER the work is "post the test result on the ticket", "test report for PROJ-123", "Test Result: PASSED/FAILED", "retest done, log it on Jira", "รายงานผลเทสลงตั๋ว", "QA report standard", or after a qa/export-evidence or page-timing run whose result belongs on a ticket. Draft first, post only after the owner says OK.
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- new-skillSkill
- agent-kit-costSkill
- agent-kit-prompt-cacheSkill
- agent-kitSkill
- containers-podmanSkill
- containersSkill
- dependency-vuln-explainerSkill
- design-coreSkill
- design-flowSkill
- devops-changeSkill
- devops-network-diagramSkill
- devops-release-scopeSkill
- devopsSkill
- documentation-doc-styleSkill
- documentation-pdf-operationsSkill
- documentationSkill
- poc-spec-driven-builderSkill
- qa-answer-reviewSkill
- qa-excel-importSkill
- qa-export-evidenceSkill
- qaSkill
- thai-mock-namingSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Colour rule: every result word is bold and coloured, in the header and in each table row:
- Very specific: line 45
Test Result takes the worst result among the judged cases, in the order FAILED > BLOCKED > NOT TESTED > PASSED.
- Very specific: line 46
NOT TESTED > PASSED. In wiki markup that is {color:#00875A}*PASSED*{color}.
- Very specific: line 55
More than one case = table: Write <dir>/cases.json from the ticket's acceptance criteria.
- Very specific: line 71
Never put code paths, API names, commit hashes or column names in case / expected / actual / steps / why: they go in tech.
- Very specific: line 98
Write it that way in actual.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
QA result comment on a ticket
S=skills/qa/ticket-report/scripts
uv run $S/ticket_report.py draft <evidence dir> --ticket PROJ-123 --env dev|uat|master|prd \
--platform "Web (admin app)" --account "<section of ~/.config/qa-ticket-report/accounts.ini>" \
--release vX.Y.Z --actual "<1-2 sentences>" [--lang th|en]
# show <dir>/ticket-report.md to the owner · on OK:
export JIRA_BASE_URL=https://<site>.atlassian.net JIRA_EMAIL=<you> JIRA_API_TOKEN=<token>
uv run $S/ticket_report.py post <evidence dir> --ticket PROJ-123 [--update <comment id>]
uv run $S/ticket_report.py --selftestaccounts.ini holds [Section] → UserName / Password and lives outside any repo.
--test-data "<text>" prints a value as-is instead.
The format
references/format.md holds the template, a filled cases.json, and the shapes that come up.
- The six header labels stay in English, exactly as written. The body follows the team's
language (
--lang thby default, Thai per thekien-thairules;--lang en). No emoji anywhere. Colour rule: every result word is bold and coloured, in the header and in each table row:
Result Colour When PASSEDgreen #00875Athe case did what Expected says FAILEDred #DE350Bit ran and did something else BLOCKEDorange #FF8B00it could not run (env down, no data, no access) NOT TESTEDgrey #6B778Cin scope but not run this round Test Result takes the worst result among the judged cases, in the order FAILED > BLOCKED > NOT TESTED > PASSED. In wiki markup that is
{color:#00875A}*PASSED*{color}.- Test Environment =
<Dev|UAT|Master|PRD> - Version <actual>. "Actual" means what the tested app reports about itself:results.jsonversionif present, else a read-only GET of the login page matched with--version-regex. Pre-release builds report a sha, so pass--releaseand the header becomesv1.2.22 (master-6ca0cf2). If the app saysv1.2.21and--releasesays something else, the draft stops. No version at all stops it too. - Test Data. On
dev/uatit shows the username and the password. Onmaster/prdthe username only, and no flag overrides that. This is the one place a test password is printed; the drafts live in a gitignored work folder, and a leak check runs before any push. - More than one case = table. Write
<dir>/cases.jsonfrom the ticket's acceptance criteria.evidencepaths are relative to<dir>(../is fine); every file has to exist.baseline: truemarks a before-the-fix run kept for comparison: shown, not judged. With nocases.json, one case is built fromresults.json(page timing: every run 2xx within--max-secondsand the same row order) or fromsteps.csv(qa/export-evidence). Write each case so a non-developer can read it in 30 seconds. Use the structured fields:
field what goes in rule casewhat is tested, in plain words no codes, ids or field names expected/actualone sentence each actualopens with the outcomestepslist, one action per item what a tester clicks or enters, in order whyonly when not PASSED; 1–2 short sentences the cause in user terms datalist of name: valuedocument number, product, account, quantity techlist, for the dev team code paths, commit, API, table/column, ids Never put code paths, API names, commit hashes or column names in
case/expected/actual/steps/why: they go intech. One fact per sentence, no sentence over ~25 words.- Images go inline, each under its case with a one-line caption. Non-image files are listed under "attached files".
- Actual Result under the header is one or two sentences with the numbers. Left out, the draft
puts
TODOthere andpostrefuses to send.
How post works
- Uploads every evidence file as
qa-<env>-<stamp>-c<case>-<name>; a name already attached is skipped, so a rerun is safe. Jira stores inline images as issue attachments. - Sends
POST /rest/api/2/issue/{key}/commentwith a wiki-markup body (!name|width=700!for images,||Test Case||…||for the table). A markdown comment cannot embed images, which is why this goes through REST v2. - Reads the comment back (
expand=renderedBody) and printsinline images N/M. N < M means an image name did not match — check the upload names.
Traps
- Every attachment must be previewable in Jira. Jira previews images, PDF, video and
text/plain;application/octet-streamorapplication/jsononly downloads.preview_mime()sends.md .json .csv .log .txt .sql .tsvastext/plain. Never hard-code a MIME type. - Draft and post are separate steps on purpose. Nothing reaches Jira before the owner reads
ticket-report.md. - A redraft keeps the upload names, so a re-post skips files already on Jira. To fix a posted
comment in place use
--update <comment id>rather than posting a second one. - A gateway 504 at exactly 60 s is the ingress cutting the request, not the API answering 504.
Write it that way in
actual.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

