When splitting a single company-managed project into two, you must determine whether the new projects can share configuration schemes (e.g., issue type scheme, workflow scheme, notification scheme) or require unique schemes to meet specific requirements. The requirement that necessitates a unique scheme isthe Fix Versions field must be mandatory for one of the projects(Option D), as this requires a distinct field configuration scheme.

Explanation of the Correct Answer (Option D):

Making theFix Versionsfield mandatory for one project but not the other requires a uniquefield configuration scheme. In Jira, field configurations control whether fields are required, hidden, or optional. A field configuration scheme maps field configurations to issue types, and each project can have its own field configuration scheme. To make Fix Versions mandatory for one project, a new field configuration must be created and associated with that project’s scheme.

Exact Extract from Documentation:

Configure field settings for a project

Field configurations define the behavior of fields (e.g., required, optional, hidden) for specific issue types. Each project can have its own field configuration scheme, which maps field configurations to issue types.

To make a field required:

Create or edit a field configuration (inSettings > Issues > Field configurations).

Find the field (e.g., Fix Versions) and mark it asRequired.

Associate the field configuration with a field configuration scheme.

Assign the field configuration scheme to the project inProject settings > Fields.If two projects need different field behaviors (e.g., Fix Versions required in one but not the other), they must use separate field configuration schemes.(Source: Atlassian Support Documentation, "Configure field settings")

Why This Fits: The requirement to make the Fix Versions field mandatory for one project but not the other cannot be achieved with a shared field configuration scheme, as field configurations apply uniformly to all projects using the same scheme. A unique field configuration scheme is necessary.

Why Other Options Are Incorrect:

Each project must use a different set of components and component leads (Option A):

Components and component leads are configured at the project level, not through a scheme. Each project can have its own components and leads without requiring a unique scheme, so this requirement does not necessitate a new scheme.

Extract from Documentation:

Manage components

Components are project-specific and configured inProject settings > Components. Each project can have its own set of components and component leads, independent of schemes.

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

Each project must send notifications from a different email address (Option B):

Notifications in company-managed projects are controlled by thenotification scheme, which defines who receives notifications for specific events. However, the email address used for sending notifications is configured at the system level (viaSettings > System > Outgoing email) or per project for custom sender addresses (if supported by the Jira instance). This does not inherently require a unique notification scheme, as the sender address is not tied to the scheme itself.

Extract from Documentation:

Configure outgoing email

The sender email address for notifications is set globally or per project inSettings > System > Outgoing email. Notification schemes define recipients, not the sender address.

(Source: Atlassian Support Documentation, "Configure email in Jira Cloud")

Sprints must be managed by a different set of users in each project (Option C):

Sprint management is controlled by permissions in thepermission scheme, specifically theManage Sprintspermission. Both projects can share the same permission scheme, as permissions can be granted to project-specific roles, groups, or users. For example, different project roles can be assigned the Manage Sprints permission in each project, allowing different users to manage sprints without requiring a unique scheme.

Extract from Documentation:

Manage sprints

TheManage Sprintspermission is granted in the permission scheme to specific roles, groups, or users. Projects can share a permission scheme, with permissions scoped to project-specific roles (e.g., Project A’s Administrators vs. Project B’s Administrators).

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

Additional Notes:

The need for a unique field configuration scheme for Option D arises because field configurations are applied at the scheme level, and a single scheme cannot have different rules (e.g., required vs. optional) for the same field across projects.

For other requirements (A, B, C), project-level settings or shared schemes with role-based scoping can accommodate the differences, making unique schemes unnecessary.