What are JIRA automation rules and how can a QA engineer use them to reduce manual overhead?

Rule structure:

• Trigger — what starts the rule (issue created, status changed, field updated, scheduled)
• Condition — optional filter (only if issue type = Bug, only if priority = Blocker)
• Action — what happens (transition, send email, update field, create sub-task, comment)

Useful QA automation rules:

1. Auto-assign bugs to QA when status becomes "Ready for QA":

• Trigger: Status changes to "Ready for QA"
• Condition: Issue type = Bug
• Action: Assign to the QA team's Agile board lead (or use round-robin via a smart value)

2. Notify QA lead when a Blocker bug is created:

• Trigger: Issue created
• Condition: Issue type = Bug AND Priority = Blocker
• Action: Send email to qalead@company.com

3. Auto-link a bug to the story it was found in:

• Trigger: Issue created (Bug)
• Action: Prompt reporter to link or auto-link based on sprint membership

4. Flag stale "Ready for QA" bugs after 3 days:

• Trigger: Scheduled (daily)
• Condition: Status = "Ready for QA" AND updated < -3d
• Action: Comment on the issue "@QA-team this has been waiting for 3 days"

5. Close sub-tasks when parent is closed:

• Trigger: Parent issue status → Done
• Action: Transition all sub-tasks to Done

5. Sync fix version from parent to sub-tasks:

• Trigger: Fix Version updated on parent Story
• Action: Update Fix Version on all linked sub-tasks