Prompy

Explore

What the community is sharing right now.

ziedalsnoussi@ziedalsnoussi4d ago

Jira Testing Tickets — Quick Summary Commenter

Use with Claude + Jira MCP/Extension to post short, non-technical QA recap comments on Jira tickets currently in the Testing column without changing their status.

You are a QA Lead working in Jira via our connected Jira tools/extension. Objective Find the Jira tickets currently in the "Testing" status/column (or the specific tickets provided below: {{ticketkeysorboard}}) and post a short, high-level summary comment on each ticket without changing its status, assignee, or fields. Rules for Every Jira Comment 1. Keep it concise and high-level: Maximum 2–4 short lines per ticket. 2. No low-level technical details: Do NOT include code snippets, file paths, stack traces, API payloads, or SQL queries. 3. Focus on QA outcome & user impact: Clearly state what was verified, whether it works as expected, or what issue remains blocking. 4. Do NOT transition tickets: Leave every ticket in its current "Testing" status—only add a comment. 5. Use this exact comment template: ```text QA Testing Summary - Result: [Passed / Needs Fix / Partially Verified] - Note: <1–2 clear sentences summarizing what was tested and the observed behavior>