A company-managed project uses a single issue type.

In a company-managed project with a single issue type, adding a second issue type is necessary when a configuration requires issue type-specific behavior that cannot be applied to the existing issue type. The requirement that necessitates a second issue type iswhen adding a new workflow(Option B), as different workflows for different issue types require separate issue types to be mapped in the project’s workflow scheme.

Explanation of the Correct Answer (Option B):

In a company-managed project, aworkflow schememaps workflows to issue types. If the project currently uses a single issue type with one workflow, adding a new workflow (e.g., for a different process) requires a second issue type to associate with the new workflow. Without a second issue type, the new workflow cannot be applied, as a single issue type can only be mapped to one workflow in a given scheme. Adding a second issue type allows the project to use both the existing workflow (for the current issue type) and the new workflow (for the new issue type).

Exact Extract from Documentation:

Configure workflow schemes

A workflow scheme maps workflows to issue types in a company-managed project.

To use a new workflow:

Create or select a new workflow inSettings > Issues > Workflows.

Update the project’s workflow scheme inProject settings > Workflowsto assign the new workflow to a specific issue type.Note: To use multiple workflows in a project, you must have multiple issue types, as each issue type can only be associated with one workflow in a scheme.(Source: Atlassian Support Documentation, "Configure workflow schemes")

Why This Fits: Adding a new workflow requires a second issue type to map the new workflow in the workflow scheme, as a single issue type cannot use multiple workflows, making Option B the correct answer.

Why Other Options Are Incorrect:

When adding a new resolution (Option A):

Resolutionsare global settings (Settings > Issues > Resolutions) that apply to all issues in a project, regardless of issue type. Adding a new resolution does not require a new issue type, as resolutions are managed at the workflow level and can be used by the existing issue type.

Extract from Documentation:

Resolutions are global and apply to all issue types. Adding a new resolution does not require new issue types.

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

When adding a new status (Option C):

A newstatuscan be added to the existing workflow for the single issue type without needing a new issue type. Statuses are part of a workflow, and the existing issue type can use the updated workflow with the new status.

Extract from Documentation:

Statuses are added to workflows, not issue types. A new status can be used by the existing issue type’s workflow.

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

When adding a new custom field (Option D):

A newcustom fieldcan be applied to the existing issue type via itscustom field contextorscreen configuration. It does not require a new issue type, as fields can be shared across or restricted to specific issue types within the same project.

Extract from Documentation:

Custom fields can be added to existing issue types via contexts or screens. New issue types are not required.

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

When adding a new security level (Option E):

A newsecurity levelin the issue security scheme applies to all issues in the project, regardless of issue type. It does not require a new issue type, as security levels are project-wide and not tied to specific issue types.

Extract from Documentation:

Security levels apply to all issues in a project and are not issue type-specific. Adding a new level does not require new issue types.

(Source: Atlassian Support Documentation, "Configure issue security schemes")

Additional Notes:

Steps to add a second issue type for a new workflow:

Add a new issue type to the project’s issue type scheme inProject settings > Issue types.

Create or select a new workflow inSettings > Issues > Workflows.

Update the workflow scheme inProject settings > Workflowsto map the new workflow to the new issue type.

These changes requireJira administratorprivileges.

The need for a second issue type arises specifically from the workflow scheme’s one-to-one mapping of workflows to issue types.