Atlassian Jira Automation Test Q&A

Q1: What is an "Incoming webhook" trigger in Jira automation?
A1: An Incoming webhook trigger allows a third-party application to trigger an automation rule by sending an HTTP POST request to a unique URL. It can specify issues to act on or provide real-time data via the {{webhookData}} smart value.

Q2: What are "Smart values" and what is their purpose?
A2: Smart values allow you to access and manipulate data within your Jira instance. They act as placeholders for dynamic data, such as {{issue.key}} or {{issue.summary}}, allowing rules to be dynamic and context-aware.

Q3: What is the "Field value changed" trigger used for?
A3: This trigger kicks off a rule when a specified field's value is modified. It supports all system and custom fields and can be narrowed down by change type (Value added, value deleted, or any changes) and operation (create, edit, transition, assign).

Q4: How do "Conditions" affect an automation rule?
A4: Conditions are used to filter which triggers continue through the automation rule. If a condition is met, the rule continues to the next component; if not, the rule stops. They allow you to add specific criteria (e.g., Priority is High) to your rules.

Q5: What does the "Branch rule / Related issues" component do?
A5: This component allows you to perform actions on issues related to the one that triggered the rule, such as sub-tasks, parent issues, epic links, or issues linked via a specific relationship. It effectively "branches" the execution to multiple issues.
