In Jira Software Cloud, automation rules usesmart valuesto reference issue fields, such as the issue key, in actions like sending emails. The correct syntax for referencing the issue key in theSend Emailaction’s subject line is{{issue.key}}(Option B).

Explanation of the Correct Answer (Option B):

The{{issue.key}}smart value retrieves the issue key (e.g., PROJ-123) of the issue that triggers or is processed by the automation rule. This can be used in the subject line of theSend Emailaction to include the issue key dynamically.

Exact Extract from Documentation:

Use smart values in automation rules

Smart values allow you to access issue fields and other data in automation actions. To reference the issue key:

Use{{issue.key}}to insert the issue key (e.g., PROJ-123) in fields like email subjects or bodies.Examples:

Email subject: Issue {{issue.key}} Updated

Output: Issue PROJ-123 UpdatedNote: Smart values are enclosed in double curly braces ({{}}). Use dotnotation to access fields (e.g., {{issue.key}}, {{issue.summary}}).(Source: Atlassian Support Documentation, "Use smart values in Jira automation")

Why This Fits: The{{issue.key}}syntax is the standard way to reference the issue key in Jira automation, making it the correct choice for theSend Emailaction’s subject line.

Why Other Options Are Incorrect:

{{triggerIssue.issuekey}} (Option A):

The{{triggerIssue}}smart value refers to the issue that triggers the rule, but the field iskey, notissuekey. The correct syntax is{{triggerIssue.key}}, not{{triggerIssue.issuekey}}. Additionally,{{issue.key}}is sufficient for most rules unless specifically targeting the trigger issue in a branched rule.

Extract from Documentation:

Use{{triggerIssue.key}}to reference the key of the issue that triggers the rule.{{issue.key}}is used for the current issue in the rule’s context.

(Source: Atlassian Support Documentation, "Use smart values in Jira automation")

{{issueKey}} (Option C):

Smart values require dot notation for field access (e.g.,{{issue.key}}).{{issueKey}}is not a valid smart value, as it does not reference a specific field.

Extract from Documentation:

Smart values must reference valid fields using dot notation (e.g., {{issue.key}}, {{issue.summary}}). Single variables like {{issueKey}} are not supported.

(Source: Atlassian Support Documentation, "Use smart values in Jira automation")

{issue.issuekey} (Option D):

The syntax uses single curly braces andissuekeyinstead ofkey, which is incorrect. Smart values require double curly braces ({{}}) and the correct field name (key).

Extract from Documentation:

Smart values use double curly braces ({{}}) and standard field names (e.g., {{issue.key}}). Incorrect formats like {issue.issuekey} will not work.

(Source: Atlassian Support Documentation, "Use smart values in Jira automation")

issue.key (Option E):

Without curly braces,issue.keyis treated as plain text, not a smart value. It will not resolve to the issue key and will appear literally in the email subject.

Extract from Documentation:

Smart values must be enclosed in {{}} to be evaluated. Plain text like issue.key will not resolve to a field value.

(Source: Atlassian Support Documentation, "Use smart values in Jira automation")

Additional Notes:

TheSend Emailaction in Jira automation allows smart values in the subject and body to dynamically include issue data.

If the rule involves branching or multiple issues,{{issue.key}}refers to the current issue in the rule’s context, while{{triggerIssue.key}}refers to the triggering issue. For a simple email rule,{{issue.key}}is typically sufficient.