Certain notification events in Jira Software Cloud are triggered only when explicitly fired by aworkflow post functionin a workflow transition. The question asks for one such event, andIssue Closedis an example of an event that is typically triggered via a post function in the workflow.
Explanation of the Correct Answer (Option B):
TheIssue Closedevent is associated with the transition of an issue to a "Closed" status in a workflow. In Jira, this event is not automatically triggered by standard issue updates (like editing fields) but is instead fired by a post function in the workflow transition that moves the issue to the "Closed" status.
Exact Extract from Documentation:
Workflow post functions and events
Post functions in a workflow transition can fire specific events to trigger notifications. For example:
TheIssue Closedevent is typically fired by a post function in the transition to a "Closed" status.
To configure this, edit the workflow transition and add a post function like"Fire a Generic Event"or select theIssue Closedevent.These events are then mapped to recipients in the project’s notification scheme.Note: Events like Issue Closed, Issue Resolved, or custom events require explicit configuration in the workflow to trigger notifications.(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
Why This Fits: The Issue Closed event is specifically tied to a workflow transition (e.g., moving an issue to the "Closed" status), and it requires a post function to fire the event. This makes it a clear example of an event triggered only by a workflow post function.
Why Other Options Are Incorrect:
Issue Deleted (Option A):
TheIssue Deletedevent is triggered when an issue is deleted from Jira (e.g., by an admin with appropriate permissions). This event is not tied to aworkflow transition or post function but is instead a system-level action.
Extract from Documentation:
TheIssue Deletedevent is triggered when an issue is permanently removed from Jira. This is a system event and does not require a workflow post function.
(Source: Atlassian Support Documentation, "Configure notification schemes")
TheIssue Updatedevent is a generic event triggered by most changes to an issue, including field updates, comments, or status changes. It does not require a post function.
(Source: Atlassian Support Documentation, "Configure notification schemes")
TheIssue Assignedevent is triggered when the assignee of an issue changes, regardless of whether it occurs in a workflow or via direct editing.
(Source: Atlassian Support Documentation, "Configure notification schemes")
TheIssue Movedevent is triggered when an issue is relocated to a different project or issue type. This is not tied to workflow post functions.
(Source: Atlassian Support Documentation, "Configure notification schemes")
Additional Notes:
Events likeIssue Closed,Issue Resolved, or custom events are typically fired by post functions because they are associated with specific workflow transitions. This distinguishes them from generic events like Issue Updated or Issue Assigned, which can be triggered by various actions.
To configure the Issue Closed event, a Jira admin would edit the workflow, add a post function to the "Close Issue" transition, and ensure the notification scheme maps the event to the desired recipients.
[:, Atlassian Support Documentation:Configure advanced work item workflows, Atlassian Support Documentation:Configure notification schemes, Atlassian Support Documentation:Manage events in Jira Cloud, ]
