A project administrator wants to modify his project screen. The project screen meets all the prerequisites for him to be able to edit it. Which two actions can he perform? (Choose two.}

When a project's screen scheme and the associated screens are not shared with any other projects, a user with the "Administer Projects" permission (i.e., a project administrator) can edit the project's screens. This capability is limited to layout and field arrangement. The project administrator can add new tabs to organize fields and can add or remove existing fields from the screen. These actions modify the presentation of information for issues within their specific project without affecting global Jira configurations.

A. create a new field: Creating a new custom field is a global action that requires Jira Administrator permissions, as it adds a new data field to the entire Jira instance.
C. set a default value for a field: Setting a default value is part of a custom field's configuration, not the screen configuration. This action requires Jira Administrator permissions.
D. make a field required: Making a field required is managed through the Field Configuration, which governs field behavior across projects. This is a Jira Administrator-level permission.

1. Atlassian Cloud Documentation, "Permissions for project administrators." This document explicitly states: "If a project's schemes are not shared with any other projects, project admins can... Edit the project's screens: Add/remove/reorder fields and tabs." This directly supports answers B and E.

2. Atlassian Cloud Documentation, "Add, edit, and remove a screen." Under the section "Edit a screen's tabs and fields," the documentation details the process of adding a tab and adding/removing a field, confirming these are standard screen editing actions.

3. Atlassian Cloud Documentation, "Create a custom field." The prerequisites section clearly states, "You must be a Jira admin to perform this function," which invalidates option A.

4. Atlassian Cloud Documentation, "Configure field layout in the issue view." This page discusses field configurations, stating, "You must be a Jira admin to configure field behavior," which includes making a field required, thus invalidating option D.