Atlassian Agile Project Management Professional Certification Practice Exam

When does an issue become unassigned after being moved to the Review column?

1. When the team agrees it’s complete

2. When a rule has been added

3. When the Product Owner approves

4. When the issue is logged as a bug

The correct answer is: When a rule has been added

In the context of Agile project management using tools like Atlassian Jira, when an issue is moved to the Review column, it typically indicates that the work on that issue is being considered for completion. An issue often becomes unassigned as part of the workflow when specific rules or automation have been set up within the project management tool. These rules can include scenarios where an issue might automatically unassign itself after being moved to the Review stage, allowing the team to dynamically reassess ownership over tasks that are under review. This practice can help in maintaining clarity around who is responsible for the next steps in the workflow, especially as it transitions from development to a review or approval phase. The unassignment can signal to team members that the issue is pending evaluation rather than under active development, which is a crucial part of the iterative process in Agile methodologies. The other options relate more to outcomes of the review process rather than the mechanics of assignment. The agreement of completion signifies a conclusion to the work but does not inherently trigger an unassignment. Product Owner approval is an important step but again does not dictate when ownership of the issue should change. Lastly, logging an issue as a bug pertains to a status change rather than assignment rules directly, as it typically means the