The latest articles on DEV Community by Nisha Bharti (@nisha_bharti_a64e3ff93251). https://dev.to/nisha_bharti_a64e3ff93251 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4193854%2F9a5ed876-8b41-4749-98e5-50968fe75470.png https://dev.to/nisha_bharti_a64e3ff93251 en Nisha Bharti Mon, 19 Oct 2026 10:15:31 +0000 https://dev.to/nisha_bharti_a64e3ff93251/where-to-put-the-human-check-when-you-combine-jira-automation-and-ai-1jpi https://dev.to/nisha_bharti_a64e3ff93251/where-to-put-the-human-check-when-you-combine-jira-automation-and-ai-1jpi <p>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.</p> <p><strong>Short answer:</strong> let AI draft, let a person approve, and only then let automation act.</p> <h2> Pattern 1: Draft, then review </h2> <p>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.</p> <h2> Pattern 2: Test on a narrow scope </h2> <p>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.</p> <h2> Pattern 3: Don't automate irreversible actions </h2> <p>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.</p> <h2> Pattern 4: Write down the assumption </h2> <p>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.</p> <h2> A quick checklist </h2> <ul> <li>Is the output visible only to staff first?</li> <li>Is the rule limited to a test scope?</li> <li>Is the action reversible?</li> <li>Is there a named reviewer?</li> </ul> <p>If you answer "no" to any of these, add a manual step.</p> <p>What's the first automation rule you would trust with an AI step?</p> <p><em>Disclosure: I work with Empyra, an Atlassian Platinum Solution Partner in Irving, Texas and Bangalore. More at <a href="[](https://www.empyra.com/atlassian-intelligence-services?utm_source=devto&amp;utm_medium=blog&amp;utm_content=N)">atlassian intelligence services</a>.</em></p> jira atlassian automation ai