ATLASSIAN Jira Administrator ACP-120 Question # 13 Topic 2 Discussion

The issue is that a custom field is visible in all company-managed projects except one, indicating a project-specific configuration is preventing the field from being displayed. The two possible reasons areScreen(Option D) andIssue layout(Option E), as these configurations control whether a field appears in a project’s issue operations or view.

Explanation of the Correct Answers:

Screen (Option D):

In company-managed projects,screensdetermine which fields are displayed during issue operations (Create, Edit, View) for specific issue types, as defined by thescreen scheme. If the custom field is not included on the screen(s) used by the problematic project’s issue types, users will not see the field when creating, editing, or viewing issues in that project. This could explain why the field is missing in one project but visible in others.

Exact Extract from Documentation:

Configure screens in company-managed projects

Screens define which fields are available during issue operations (Create, Edit, View). Each project uses a screen scheme to map screens to issue types and operations.

If a field is not on a project’s screen:

Users cannot see or interact with the field in that project.To check:

Go toProject settings > Screens.

Verify if the custom field is included on the relevant screens.Note: A field must be on the screen to be visible during issue operations.(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")

Why This Fits: If the custom field is not on the screen(s) used by the project, it will not be visible, makingScreena possible reason for the issue.

Issue layout (Option E):

Theissue layoutin a company-managed project controls which fields are displayed, hidden, or placed in the context panel in the issue view. If the custom field is moved to theHidden fieldssection in the issue layout for the problematic project, users will not see it when viewing issues, even if the field is on the screen and contains data. This could explain the field’s absence in one project.

Exact Extract from Documentation:

Configure issue layouts in company-managed projects

Issue layouts determine which fields are displayed or hidden in the issue view.

To hide a field:

Go toProject settings > Issue layout.

Move the field to theHidden fieldssection.Impact: Hidden fields are not shown in the issue view, even if they areon the screen and have values.Note: Issue layouts are project-specific and can differ between projects.(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")

Why This Fits: If the custom field is hidden in the issue layout for the problematic project, it will not be visible in the issue view, makingIssue layouta possible reason.

Why Other Options Are Incorrect:

Groups (Option A):

Groups are used in permission schemes or field configurations to control access or behavior, but they do not directly determine field visibility. If the field is visible in other projects, the issue is not group-related, as groups apply globally or via schemes shared across projects.

Extract from Documentation:

Groups are used for permissions or field restrictions, not for controlling field visibility on screens or layouts.

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

Project roles (Option B):

Project roles are used in permission schemes to grant permissions (e.g.,Edit Issues). They do not control whether a field is displayed on a screen or in the issue layout. The issue is about visibility, not permissions.

Extract from Documentation:

Project roles manage permissions, not field visibility. Check screens or issue layouts for display issues.

(Source: Atlassian Support Documentation, "Manage project roles")

Security levels (Option C):

Security levels (part of an issue security scheme) restrict which issues a user can view, not which fields are displayed within an issue. If users can see issues but not the field, security levels are not the cause.

Extract from Documentation:

Issue security levels control issue visibility, not field visibility within an issue.

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

Validator (Option F):

Validators ensure conditions are met before a workflow transition (e.g., a field is filled). They do not affect whether a field is visible in the issue view or during operations.

Extract from Documentation:

Validators enforce conditions during transitions, not field visibility.

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

Step property (Option G):

Step properties (workflow properties) control behaviors like editability in a status (e.g.,jira.issue.editable). They do not directly control field visibility on screens or in the issue view.

Extract from Documentation:

Workflow properties manage status behaviors, not field visibility. Use screens or issue layouts for display issues.

(Source: Atlassian Support Documentation, "Use workflow properties")

Additional Notes:

To resolve the issue, check:

Project settings > Screens: Ensure the custom field is on the relevant screen(s) for the project’s issue types.

Project settings > Issue layout: Verify the field is not in theHidden fieldssection.

These configurations requireproject admin(for issue layout) orJira administrator(for screens) privileges.

Other potential causes (not listed) includefield configurations(if the field is hidden for all issue types in the project), but screens and issue layouts are the most direct reasons.