All company-managed projects share the same permission scheme and workflow scheme.

To restrict theNeeds Auditworkflow transition to auditors across all company-managed projects, which share the same permission and workflow schemes, auditors should be configuredas a group(Option B). This allows the group to be referenced in a workflow condition to limit access to the transition efficiently across all projects.

Explanation of the Correct Answer (Option B):

The requirement to restrict theNeeds Audittransition to auditors can be achieved by adding aconditionto the transition in the shared workflow scheme. A common condition, such asUser Is In Group, restricts the transition to members of a specific group.

Since all projects share the same workflow scheme, configuring auditors as a group (e.g., “Auditors”) allows you to create the group once, add all auditors to it, and reference it in the workflow condition. This ensures that only auditors can use theNeeds Audittransition across all projects.

Exact Extract from Documentation:

Configure workflow conditions

Conditions restrict who can perform a workflow transition in a company-managed project.

To restrict a transition:

Go toSettings > Issues > Workflows.

Edit the workflow and select theNeeds Audittransition.

Add a condition, such asUser Is In Group, and select the group (e.g., Auditors).Note: Using a group is efficient for managing permissions or conditions across multiple projects with a shared workflow scheme.(Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Why This Fits: Configuring auditors as a group allows a single workflow condition to restrict theNeeds Audittransition to group members across all projects, meeting both requirements efficiently.

Why Other Options Are Incorrect:

As a User custom field (Option A):

AUser custom field(e.g., User Picker) stores a single user for an issue and is not suitable for defining a set of users who can perform a workflow transition. Workflow conditions cannot reference custom fields to restrict transitions.

Extract from Documentation:

User custom fields store user data for issues but cannot be used in workflow conditions to restrict transitions.

(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")

As a Group custom field (Option C):

AGroup custom field(e.g., Group Picker) stores a group for an issue, but workflow conditions typically reference groups directly, not group picker fields. This approach is unnecessary and overly complex for restricting transitions.

Extract from Documentation:

Group custom fields are not used for workflow conditions. Use direct group references for transition restrictions.

(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")

As single users (Option D):

Configuring auditors as individual users in a workflow condition (e.g.,User Is In Any Users) is inefficient, as it requires listing each auditor manually. This approach does not scale well for multiple auditors working across all projects and is prone to maintenance issues if auditors change.

Extract from Documentation:

Listing individual users in conditions is not recommended for scalability. Use groups for managing multiple users across projects.

(Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Additional Notes:

Steps to configure:

Create an “Auditors” group inSettings > User management > Groups.

Add all auditors to the “Auditors” group.

Edit the shared workflow inSettings > Issues > Workflows.

Add aUser Is In Groupcondition to theNeeds Audittransition, selecting the “Auditors” group.

Configuring the group and workflow requiresJira administratorprivileges.

The shared workflow scheme ensures the condition applies to all projects.