ACP-120 general project configuration: what the exam tests

Change the configuration of one space that shares its setup, and every space sharing it changes too. A team-managed space shares nothing, so you can change it without touching any other space.

01 What does ACP-120 test about general project configuration?

You read a stem where an admin edits one space and other spaces change too, and it looks like a bug. Here that is expected, and the exam wants you to know which kind of space behaves that way.

Questions also cover space details such as keys and the default assignee, and feature toggles and versions.

What the exam asks about in this domain

1. 01Space typesShared configuration versus self-contained team-managed spaces
2. 02Space detailsKeys, names, categories, default assignee and email
3. 03Features and versionsFeature toggles, version dates and releases

Know space types, space details, and features and versions.

02 How do the two space types handle configuration?

Team-managed spaces share no configuration and turn features on with toggles.

Company-managed and team-managed configuration

Company-managed

• Can share configuration with other spaces
• Custom fields mapped through schemes
• Fields usually shared across spaces

Team-managed

• Shares no configuration
• Custom fields bound to the space
• Features turned on with toggles

Only Jira admins can create a space with a shared configuration, and that option is not on the Free plan. In team-managed spaces, custom fields belong to the space and cannot be shared.

With a shared configuration, one change affects every space that shares it.

03 Which space details trip people up?

New spaces start with the default assignee set to Unassigned. That value is possible only if Allow unassigned work items is on in Jira's general configuration; otherwise it is the space owner.

After you change a team-managed space key, the new key can take up to 10 minutes to show on the board. Deleting an old key from Previous keys restricts access to work items that refer to it.

If the default assignee will not change, check Allow unassigned work items.

04 How do features and versions work?

In a team-managed space, features such as sprints and estimation are toggled on the Features page, and estimation lets the team calculate velocity.

A Scrum version is planned ahead and released when its work is done, while a Kanban version can be released at any time. An unreleased version past its release date is highlighted as overdue.

Kanban versions can be released at any time; Scrum versions wait for the planned work.

Summary

1. Only Jira admins can create spaces with a shared configuration.
2. Team-managed custom fields stay inside their own space.
3. A changed team-managed space key can take up to 10 minutes to reach the board.

Sources

1. Create a new space | Jira Cloud | Atlassian Support
2. Manage and administer team-managed spaces | Jira Cloud | Atlassian Support
3. Configure a space | Atlassian Support
4. Release your team's work in versions | Jira Cloud | Atlassian Support
5. Create and edit team-managed spaces | Jira Cloud | Atlassian Support
6. Enable agile features in team-managed spaces | Jira Cloud | Atlassian Support
7. How do work types differ based on space type? | Jira Cloud | Atlassian Support