In a company-managed project, theissue layoutdetermines how fields are displayed in the issue view (e.g., which fields are visible, hidden, or in the context panel). The true statement is thatyou can copy a layout to another project using the same screen(Option B), as Jira allows copying issue layouts to streamline configuration across projects.
* Explanation of the Correct Answer (Option B):
* Theissue layoutin a company-managed project is configured inProject settings > Issue layout and is tied to a screen (via the screen scheme). Jira allows copying an issue layout to another project that uses the same screen, ensuring consistent field arrangements across projects.
* Exact Extract from Documentation:
Configure issue layouts in company-managed projects
Issue layouts define which fields are displayed, hidden, or placed in the context panel in the issue view.
To copy a layout:
* Go toProject settings > Issue layout.
* SelectCopy layoutand choose another project that uses the same screen.Note: The target project must use the same screen (via its screen scheme) for the layout to be compatible.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Why This Fits: Copying an issue layout to another project using the same screen is a supported feature, making Option B the correct answer.
* Why Other Options Are Incorrect:
* You can reuse fields from a team-managed project (Option A):
* Fields in team-managed projects are project-specific and cannot be reused in company- managed projects. Company-managed projects use global custom fields or system fields, managed inSettings > Issues > Custom fields. Fields from team-managed projects are isolated and not accessible.
* Extract from Documentation:
Custom fields in team-managed projects are project-specific and cannot be reused in company-managed projects. Company-managed projects use global custom fields.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* You can move any field to the Hidden fields section (Option C):
* Not all fields can be moved to theHidden fieldssection. System fields likeSummary,Issue Type, andStatusare required and cannot be hidden. Only non-mandatory fields (e.g., custom fields, non-required system fields) can be hidden.
* Extract from Documentation:
In the issue layout, you can hide non-mandatory fields by moving them to theHidden fieldssection. Required fields like Summary, Issue Type, and Status cannot be hidden.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* You can move any field to the Context fields section (Option D):
* TheContext fieldssection (right panel in the issue view) has restrictions on which fields can be placed there. Fields likeSummary,Description, and certain system fields cannot be moved to the context panel, as they are designed for the main issue view. Only eligible fields (e.g., custom fields, Labels, Components) can be moved to theContext fieldssection.
* Extract from Documentation:
TheContext fieldssection is for fields like Labels, Components, or custom fields. Core fields like Summary and Description cannot be moved to the context panel.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Additional Notes:
* Configuring issue layouts requiresproject adminprivileges for the project (Project settings > Issue layout).
* Copying layouts is useful for maintaining consistency across projects with similar configurations.
:
Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Atlassian Support Documentation:Manage custom fields in Jira Cloud