To use a newly added custom field in a company-managed project, you must ensure it appears on the appropriate screens (e.g., Create, Edit, View) for the project’s issue types. The configuration that must be modified is thescreen(Option B), as the field needs to be added to the screen(s) used by the project.

Explanation of the Correct Answer (Option B):

The custom field is already available to all issue types and projects, meaning itscontextis configured globally. To make the field usable in your company-managed project, it must be added to thescreenassociated with the project’s issue types (via thescreen scheme). Screens determine which fields are displayed during issue operations (Create, Edit, View), and adding the custom field to the relevant screen ensures users can interact with it.

Exact Extract from Documentation:

Add a custom field to a screen

To use a custom field in a project, it must be added to the screens used for Create, Edit, or View operations.

To add a field:

Go toSettings > Issues > Screens.

Select the screen associated with the project’s issue types.

Add the custom field to the screen.Note: Ensure the screen is part of the project’s screen scheme (Project settings > Screens). If the field is not on the screen, it will not appear during issue operations.(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")

Why This Fits: Adding the custom field to the project’s screen is a necessary configuration to make it usable, as it ensures the field is visible and editable, meeting the requirement to use the field in the project.

Why Other Options Are Incorrect:

Field configuration (Option A):

Field configurationscontrol whether a field is required, optional, or hidden. While you might later adjust the field’s behavior (e.g., make it required), the field is already available and does not require field configuration changes to be used initially. Adding it to a screen is the primary step.

Extract from Documentation:

Field configurations manage field behavior (e.g., required, hidden). Adding a field to a screen is required before configuring its behavior.

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

Custom field context (Option C):

The custom field’scontextis already configured to include all issue types and projects, so no changes are needed here. Contexts define the projects and issue types a field applies to, and this is already set correctly.

Extract from Documentation:

Custom field contexts define where a field is available. If a field is already available to all projects and issue types, no context changes are needed.

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

Issue layout (Option D):

Theissue layoutcontrols which fields are displayed or hidden in the issue view and filter results. While you might later adjust the issue layout to show the field in the issue view, the initial step to use the field is adding it to the screen for Create/Edit operations. The screen configuration is more fundamental.

Extract from Documentation:

Issue layouts control field visibility in the issue view. Fields must first be added to screens for Create/Edit operations before appearing in the issue layout.

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

Additional Notes:

Steps to configure:

Identify the screen(s) used by the project’s issue types inProject settings > Screens.

Go toSettings > Issues > Screens, select the relevant screen, and add the custom field.

Configuring screens requiresJira administratorprivileges.

After adding the field to the screen, you may also configure theissue layoutorfield configurationfor additional control, but the screen is the first required step.