ACP-120 issue types, fields, screens: what the exam tests

The exam guide makes Jira Cloud admins responsible for issue types, fields, screens and their schemes. In a team-managed space you can add up to 30 work types, but only standard ones.

01 What does ACP-120 test about issue types, fields and screens?

You know where issue layouts live in a company-managed space, then a mock exam question asks about a team-managed one. The exam guide expects you to configure issue layouts in both team-managed and company-managed spaces. It also asks you to know how to use custom field context.

In team-managed spaces, work types and custom fields also come with limits you need to know.

What the exam asks about in this domain

1. 01Work typesStandard, parent and subtask types, limits and restrictions
2. 02Custom fieldsUse cases, field context and team-managed field limits
3. 03Screens and layoutsIssue layouts in both space types, plus screens and their schemes

Know work types, custom fields with context, and screens and layouts.

02 How do work types work in team-managed spaces?

A team-managed space holds up to 30 work types, and you can create only custom standard types, not parent or subtask types. Roadmaps and reports need the suggested Epic type, not a custom type named Epic.

Subtasks are enabled by default and can sit under stories, bugs or tasks, but not directly beneath an Epic.

Custom team-managed work types are always standard types.

03 How do custom fields differ between space types?

Custom fields in the two space types

Company-managed

• Suits shared field customizations
• Context covers chosen work types
• Fields placed on screens

Team-managed

• Fields belong to one space
• Up to 50 custom fields
• Fields added to work types

A field created in a team-managed space cannot be shared with any other space. Moving to a company-managed space means a Jira admin recreates each field, updates its context to cover the right work types and adds it to the correct screens.

Team-managed fields stay in their space; company-managed fields need context and screens.

04 Which field rules catch people out?

When a field appears on several work types in a team-managed space, renaming it on one renames it on all. Checkbox and dropdown fields share their options but can have a different default on each work type.

Marking a field Required stops new work items of that type from being created until it is filled in, and Summary is always required.

Shared team-managed fields share a name; checkbox and dropdown defaults can differ per work type.

Summary

1. Team-managed spaces allow up to 30 work types.
2. Team-managed spaces allow up to 50 custom fields.
3. Team-managed subtasks cannot sit directly beneath an Epic.

Sources

1. ACP-120 Exam Topics V2 Version Date: April 2025 1 Access, Permissions, Security (28% of the exam)
2. Set up work types in team-managed spaces | Jira Cloud | Atlassian Support
3. Customize work item fields in team-managed spaces | Jira Cloud | Atlassian Support
4. Manage subtasks in team-managed spaces | Jira Cloud | Atlassian Support
5. Migrate between team-managed and company-managed spaces | Jira Cloud | Atlassian Support