← ClaudeAtlas

qa-ticket-reportlisted

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.
th3r-dev/th3-skills · ★ 2 · Data & Documents · score 66
Install: claude install-skill th3r-dev/th3-skills
# QA result comment on a ticket ```bash 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 --selftest ``` `accounts.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 th` by default, Thai per the `kien-thai` rules; `--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 | |---|---|---| | `PASSED` | green `#00875A` | the case did what Expected says | | `FAILED` | red `#DE350B` | it ran and did something else | | `BLOCKED` | orange `#FF8B00` | it could not run (env down, no data, no access) | | `NOT TESTED` | grey `#6B778C` | in scope but not run this round | Test Re