You must add a new issue type to an existing company-managed project.

Adding a new issue type to a company-managed project requires updating configurations that map issue types to various settings (e.g., screens, workflows, fields). The configuration item that isdefinitely not impactedis theissue security scheme(Option C), as it controls issue visibility and is not directly tied to issue types.

Explanation of the Correct Answer (Option C):

Anissue security schemedefines security levels that restrict which users can view issues in a project, based on criteria like users, groups, or roles. It is applied at the project level and is not specific to issue types. Adding a new issue type does not require changes to the issue security scheme, as security levels apply to all issues in the project regardless of their type.

Exact Extract from Documentation:

Configure issue security schemes

Issue security schemes define security levels to control who can view issues in a project.

Impact of issue types:

Security levels are applied to all issues in a project, regardless of issue type.

Adding a new issue type does not affect the issue security scheme.To check:

Go toProject settings > Issue security.

Review the security levels and their criteria.Note: Issue security is independent of issue type configurations.(Source: Atlassian Support Documentation, "Configure issue security schemes")

Why This Fits: Theissue security schemeis not impacted by adding a new issue type, as it operates at the project level and does not depend on issue type configurations, making Option C the correct answer.

Why Other Options Are Incorrect:

Issue layout (Option A):

Theissue layoutdefines which fields are displayed or hidden in the issue view for each issue type. Adding a new issue type may require configuring a new issue layout to specify field visibility for that type, impacting this configuration.

Extract from Documentation:

Issue layouts are configured per issue type inProject settings > Issue layout. Adding a new issue type may require a new layout configuration.

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

Issue type screen scheme (Option B):

Theissue type screen schememaps screens to issue types for operations (Create, Edit, View). Adding a new issue type requires assigning a screen to it in the scheme, impacting this configuration.

Extract from Documentation:

Adding a new issue type requires updating the issue type screen scheme to assign screens for the new type.

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

Workflow scheme (Option D):

Theworkflow schememaps workflows to issue types. Adding a new issue type requires assigning a workflow to it in the scheme, impacting this configuration.

Extract from Documentation:

Adding a new issue type requires updating the workflow scheme to assign a workflow for the new type.

(Source: Atlassian Support Documentation, "Configure workflow schemes")

Field configuration scheme (Option E):

Thefield configuration schememaps field configurations to issue types, defining field behavior (required, optional, hidden). Adding a new issue type may require assigning a field configuration to it, impacting this configuration.

Extract from Documentation:

Adding a new issue type may require updating the field configuration scheme to assign a configuration for the new type.

(Source: Atlassian Support Documentation, "Configure field settings")

Additional Notes:

Steps to add a new issue type:

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

Update theissue type screen scheme,workflow scheme, andfield configuration schemeto include the new issue type.

Configure theissue layoutfor the new issue type if needed.

These changes requireJira administratorprivileges for schemes andproject adminprivileges for issue layout.

Theissue security schemeremains unaffected, as it applies to all issues in the project.