In team-managed projects, workflows are simplified and configured withinProject settings > Workflow. Users (typically project admins) can add rules to transitions, such as clearing fields, restricting transitions, or setting field values. However, team-managed workflows do not support complex automation-like rules, such as automatically reopening Sub-tasks when a Story is reopened, as this requires interacting with related issues (Sub-tasks), which is not supported out-of-box in team-managed workflow rules.
Explanation of the Correct Answer (Option B):
The rule toreopen Sub-tasks when reopening Storiesrequires a workflow rule to detect the transition of a Story to an open status and then automatically transition its Sub-tasks to an open status. Team-managed workflows do not support rules that affect related issues (e.g., Sub-tasks) during a transition. This functionality requires Jira automation or a company-managed project workflow with custom post functions, which are not available in team-managed projects.
Exact Extract from Documentation:
Configure workflows in team-managed projects
Team-managed projects use simplified workflows that allow adding rules to transitions, such as:
Restricting transitions to specific users or roles.
Setting or clearing field values (e.g., Assignee, Description).
Requiring fields to be filled.Rules are limited to the issue being transitioned and cannot affect related issues (e.g., Sub-tasks, Epics). To automate actions on related issues, use Jira automation rules.Note: Team-managed workflows are project-specific and edited inProject settings > Workflow.(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
Why This Fits: The rule to reopen Sub-tasks requires interacting with related issues (Sub-tasks), which is beyond the capabilities of team-managed workflow rules, making Option B the correct answer.
Why Other Options Are Incorrect:
Rule to clear the Assignee when closing (Option A):
Team-managed workflows support rules to clear fields during a transition. A rule can be added to the transition to theClosedstatus to clear theAssigneefield.
Extract from Documentation:
You can add a rule to a transition to clear a field, such as Assignee, when moving to a status like Closed.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
Add a rule to restrict a transition to a specific user (e.g., Peter) or role, ensuring only they can move issues to a status like Approved.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
Rules can clear fields like Description during a transition, such as when reopening an issue.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
Restrict a transition to the Reporter to ensure only they can move issues to a status like Closed.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
Additional Notes:
Team-managed workflows are designed for simplicity, with rules limited to the issue being transitioned. Complex logic, such as affecting Sub-tasks (Option B), requires Jira automation rules, which are separate from workflow rules.
Peter, as a project admin in a team-managed project, can edit the workflow inProject settings > Workflow.
[:, Atlassian Support Documentation:Configure workflows in team-managed projects, Atlassian Support Documentation:Automate your Jira Cloud instance, ]