結合 Jira Automation 與 AI 時，人工審核應設在哪裏？
Where to Put the Human Check When You Combine Jira Automation and AI
結合 Jira 自動化與 AI 時，應由 AI 起草、人工審批，再讓自動化執行，避免小錯誤在數百張工單中重複發生。使用 AI 生成的查詢時，先在單一專案或加入標籤條件測試，並檢查最初幾次執行的 audit log。大量轉換狀態、刪除及面向客戶的電郵應先經人工審批，並在規則説明中記下預期輸出和審核人。
Automation rules do exactly what you tell them. AI-generated text and queries can be close but not quite right. Put them together and a small error can repeat across hundreds of issues.
Short answer: let AI draft, let a person approve, and only then let automation act.
Pattern 1: Draft, then review
If a rule posts an AI-written summary to a ticket, have it post as an internal comment first. A person reads it and decides whether to share it with the customer.
Pattern 2: Test on a narrow scope
When a rule uses a generated query, run it on one project, or add a label condition, before widening it. Check the audit log after the first few runs.
Pattern 3: Don't automate irreversible actions
Bulk transitions, deletions and customer-facing emails should wait for a person's sign-off. Comments and labels are easy to undo, so they are safer starting points.
Pattern 4: Write down the assumption
Add a note in the rule description: what the AI step is expected to produce and who reviews it. Six months later, someone will need to know.
A quick checklist
- Is the output visible only to staff first?
- Is the rule limited to a test scope?
- Is the action reversible?
- Is there a named reviewer?
If you answer "no" to any of these, add a manual step.
What's the first automation rule you would trust with an AI step?
Disclosure: I work with Empyra, an Atlassian Platinum Solution Partner in Irving, Texas and Bangalore. More at atlassian intelligence services.
來源：DEV Community · dev.to