Free Atlassian ACP-620 Exam Dumps May 2026

The rule is triggered when an issue is created, and likely includes an action to assign the issue. If the rule previously worked but now fails with errors, and the rule is still enabled, a common cause is that the user executing the rule (Atalie) lost the Assign Issues permission, preventing the assignment action from succeeding.

The correct rule must:

Trigger when an issue is moved from PR to PD

Act on all sub-tasks of that issue

Add a comment to each sub-task

Chosen option correctly uses a branch rule for related issues (Sub-tasks), which ensures that the comment is applied to each sub-task of the moved issue. The other rules apply conditions to the main issue only, not its sub-tasks.

Created vs. Resolved Issues Report: This report depends on the Resolved status to track when issues are considered resolved. Removing the status may impact the accuracy of this report.

Column mapping on the project board: If Resolved was previously mapped to a column, you must update the board's column mapping to reflect the workflow change and prevent unmapped statuses.

When multiple components are selected on issue creation, Jira cannot determine a single default assignee if each component has a different assignee rule. In this case:

Hardware Component lead (Vincent Choy)

Software Project default (Alana Grant)

Infrastructure Unassigned

Since the assignee logic conflicts, Jira defaults to Unassigned to avoid ambiguity.