General project configuration in Jira Cloud: choose team-managed or company-managed spaces, change a space name or key, release versions, set default assignees.
Every point below comes from Atlassian's official documentation; each section lists its sources.
Think first How do you choose between a team-managed and a company-managed space, and between Scrum and Kanban?
Why it matters: Questions describe a team's needs and ask which space type, template or board style fits, or what a shared configuration changes.
The two space types differ mainly in who administers them. Company-managed spaces share schemes and fields across many spaces, set up by Jira admins. Team-managed spaces keep their own configuration, so a team can change it without a Jira admin.
Step 2 of 10
Term
Meaning
Company-managed space
A space, formerly called classic, whose schemes and custom fields Jira admins set up and often share.
Team-managed space
A space, formerly called next-gen, whose configuration is its own and is not shared with other spaces.
Scheme
A mapping Jira admins use to tie settings, such as custom fields, to a company-managed space's work types.
Template
The starting setup you pick when you create a space, such as Scrum or Kanban.
Step 3 of 10
The key difference is how each space type is administered. Company-managed spaces were once called classic, and team-managed spaces next-gen. In a team-managed space, anyone can run their team's work and process without a Jira admin.
Team-managed and company-managed spaces compared
Feature
Team-managed
Company-managed
Who configures it
The team itself, without a Jira admin
Jira admins, through schemes
Custom fields
Bound to the space and not shareable
Usually shared across many spaces
Effect of a change
No other space is affected
Shared fields reach every space that uses them
Step 4 of 10
Company-managed spaces share fields and schemes across spaces. Jira admins map settings, such as custom fields, to work types through schemes. This suits a team that needs advanced or shared field customizations across all users.
Exam trap A space admin cannot change company-managed statuses or workflows. Only Jira admins create and modify them.
Step 5 of 10
Changes to a team-managed space affect no other space. Its configuration is its own. Custom fields you add stay bound to that space, so other spaces on the site cannot reuse them.
Exam trap Team-managed custom fields cannot be shared. When fields must be shared across all users, pick a company-managed space.
Step 6 of 10
Any user can create a team-managed space by default. That includes non-admins. A Jira admin who wants to restrict this removes the Create team-managed spaces permission.
Step 7 of 10
Pick a template first, then choose how the space is managed. After Create space, choose a Work management or Software development template and select Use template. Or choose the team-managed type first, then use Change template for Scrum or Kanban.
Step 8 of 10
Scrum boards wait for sprints; Kanban boards cap and clear work. With Sprints enabled, the board shows no work items until a sprint starts. On a Kanban board, you can set a column limit, and Done items clear every 14 days.
Exam trap Team-managed spaces do not support parallel sprints. A team that must run sprints side by side cannot do it there.
Step 9 of 10
Jira cannot convert a team-managed space to company-managed. A Jira admin has to create a new company-managed space by hand. So choose the space type carefully at the start.
Exam trap There is no native convert option. Moving to company-managed means a Jira admin creates a new space manually.
Step 10 of 10
The key difference between the two space types is how they are administered.
Choose company-managed when fields must be shared or customized across all users.
A team-managed change never affects other spaces, and its custom fields cannot be shared.
Team-managed spaces do not support parallel sprints.
No native feature converts team-managed to company-managed; a Jira admin builds a new space.
Think first Why is renaming a space easy, while changing its key needs a plan?
Why it matters: Questions describe a change to a space's name, key or details and ask what breaks, what keeps working and who can do it.
A space name is a label, and filters pick up a new name on their own. A space key shows up in work item keys such as DEMO-1, so changing it touches links, filters and queries. Jira softens this by saving previous keys.
Step 2 of 10
Term
Meaning
Space key
The short uppercase code of a space, such as DEMO, used in work item keys.
Previous space key
An old key Jira saves after a key change so existing links and queries keep working.
Default assignee
Who a new work item goes to when nobody is chosen: Unassigned or the Space owner.
Space details
The Space settings page where you edit a space's details and select Save details; team-managed spaces set their category there.
Step 3 of 10
Open Space settings, then Details, and select Save details. Space admins can edit the name, description, avatar, URL and lead without the Administer Jira global permission. They can only view the space's schemes, not select or edit them.
Step 4 of 10
A new space name updates in filters automatically. Filters across the Jira site show the new name without any extra work. A key change is different: board filters and dashboard filter gadgets then need the new key.
Step 5 of 10
Changing a key is for organization, site or Jira admins. Editing a key is not a simple task. A new key must be at least two characters, start with an uppercase letter, and use only uppercase letters or numbers.
Exam trap Being a space admin is not enough to change a space key. That needs an organization, site or Jira admin.
Step 6 of 10
Old links keep working, but saved queries need the new key. Jira saves previous keys automatically. Confluence work item macros also keep working, though the cache may take time to refresh.
What a space key change does to existing items
Item
After the key changes
What you do
Links to work items such as EXAMPLE-1
Still open the work item, now DEMO-1
Nothing; link aliases are not updated
Confluence work item macros
Keep working
Allow time for the cache to refresh
Board filters and dashboard filter gadgets
Need the new key
Update them, and tell your users
Step 7 of 10
An old key cannot go to a new space while still saved. It becomes available only if you delete the space it belonged to, or delete it from previous keys. Deleting a previous key can affect links, board filters, dashboard gadgets and JQL queries that still use it.
Exam trap Deleting a previous key is not harmless cleanup. Anything still using that key, such as links or JQL queries, can be affected.
Step 8 of 10
The default assignee is either Unassigned or the Space owner. New spaces start with Unassigned. Unassigned is only possible when Allow unassigned work items is on in general configuration. To make a specific person the default, change the Space owner.
Exam trap You cannot pick any named person as a space's default assignee. You change the Space owner instead.
Step 9 of 10
Company-managed categories are assigned by a Jira admin. In a team-managed space, you set the category yourself under Details. Space URLs exist only in company-managed spaces and show in the Spaces directory.
Step 10 of 10
A space rename updates in filters automatically; a key change needs filters and gadgets updated.
Only organization, site and Jira admins can edit or delete a space key.
Previous keys are saved, so old links and queries keep working after a key change.
The default assignee can only be Unassigned or the Space owner.
Think first What should a Jira admin check before releasing a version, and who is allowed to create, edit and release one?
Why it matters: Questions describe a release situation and ask which permission, step or setting decides what happens to its work items.
A version groups features and fixes that ship together as one update. Admins set it up, track its progress on the release hub, and release it. At release time, Jira asks what to do with work that is still unresolved.
Step 2 of 9
Term
Meaning
Version
A set of features and fixes that ship together as a single update to your app.
Fix versions field
The work item field that links a work item to one or more versions.
Release hub
The page that summarizes a version's work items so you can spot remaining work.
Driver
The space admin who coordinates a release from start to finish.
Step 3 of 9
Only a Space admin can enable the releases feature. Once it is on, every work type in the space gains a Fix versions field. That field is how work items join a version, and one item can sit in several versions.
Step 4 of 9
Each version task has its own permission. Adding a work item to a version needs Edit work items. Creating or editing a version needs Space admin or Manage versions. Releasing is the strictest: it needs space admin rights.
Exam trap Manage versions lets a user create or edit a version, but it does not let them release it. Releasing needs space admin permissions.
Step 5 of 9
Pick a name your teammates will recognize at a glance. The Start Date makes the Version Report more accurate when work begins long after planning. The End Date drives the days remaining shown on the Release Hub. The Driver defaults to whoever created the version.
Step 6 of 9
The release hub shows whether any work remains. It gives a summary and a breakdown of the version's work items. In the scrum version panel, a version with at least 1 work item shows a progress bar by status category. You can also search with the fixVersion JQL field.
Exam trap A done work item can still raise a warning on the release page when its pull request is open. Open review warnings, by contrast, need a Fisheye-Crucible integration.
Step 7 of 9
Releasing asks what to do with unresolved work items. Open the Releases tab, pick the version, select its status such as Unreleased, then choose Release. Jira then asks how to handle unresolved items and for a release date. Approval is optional unless Require approvals was ticked.
Exam trap Require approvals does not apply to every release. A version can be released without approval unless that checkbox was selected in the create or edit Release modal.
Step 8 of 9
Scrum plans a version ahead; Kanban releases whenever you choose. Kanban suits continuous flow, so items need no version up front. On a company-managed Kanban board, released items leave the board once all their fix versions ship.
How versions behave on Scrum and Kanban
Feature
Scrum
Kanban
When to release
When the planned work is complete
At any time you choose
What the version holds
The work planned for it in advance
All work complete at release time
Exam trap The Kanban Release menu does not list every unreleased version. It shows only versions assigned to at least 1 work item in the Done column.
Step 9 of 9
Releasing a version needs space admin permissions; Manage versions only covers create and edit.
At release, you decide what happens to unresolved work items and enter a release date.
Check the release hub first: it shows any remaining work in the version.
A Kanban version can be released at any time and holds all work complete at that moment.
Think first When a work item has several components, who ends up as its assignee, and why?
Why it matters: Questions describe a space's components and default assignees and ask who Jira assigns a new work item to.
Each component can carry its own default assignee. That component setting wins over the space's overall default assignee. When several components disagree, alphabetical order decides.
Step 2 of 8
Term
Meaning
Component
A part of a company-managed space that work items link to through the Component field.
Default assignee
The person a new work item is assigned to when created with a component.
Space default assignee
The space's overall default assignee, used unless a component default overrides it.
Component lead
The person, usually a team lead, who oversees work linked to a component.
Step 3 of 8
Components exist only in company-managed spaces. Each component is scoped to the space it was created in. Space admins configure them, and they can do so without the Administer Jira global permission. Everyone else in the space can view, search and link work items to them.
Step 4 of 8
A component offers several default assignee choices. You can pick a named person or a role. A role keeps working when someone leaves a team that changes often.
What each component default assignee option does
Option
Who gets the work item
Depends on
Component lead
The component's lead
A lead being set on the component
Space owner
The owner of the space
Who owns the space
Space default
Whoever the space's default assignee is
The space's default assignee
Unassigned
Nobody, if the site allows unassigned work items
The site allowing unassigned work items
Exam trap Unassigned is not guaranteed. The work item stays unassigned only when the site allows unassigned work items.
Step 5 of 8
A component default assignee overrides the space default assignee. With the Space default option, the component sends the work item to the space's default assignee. A component default set to anyone else takes priority over the space default.
Exam trap Many candidates expect the space default to win because it is set higher up. It is the other way round: the component setting takes priority.
Step 6 of 8
With conflicting defaults, the alphabetically first component wins. Say a work item gets components named Backend and Mobile with different default assignees. Jira assigns it to the Backend default assignee, because Backend comes first alphabetically.
Exam trap The order you select the components in does not matter. Jira uses the component name that comes first alphabetically.
Step 7 of 8
A space can hold up to 10,000 Jira components. At that limit, admins cannot create more components until usage drops. Existing components and work items stay available. Compass components do not count toward this limit.
Step 8 of 8
A component default assignee overrides the space's overall default assignee.
With several components and different defaults, the alphabetically first component decides.
Use a role as default assignee when the team changes often.
Components exist only in company-managed spaces, scoped to their own space.
Each topic's Check tested it on its own; this mixes them.
Mixed quiz
Take the Domain 2 quiz
7 questions mixed from every topic in this domain, each answer explained. Mixing topics is harder than one at a time, and it is what the exam does. No account needed; with a free account your answers also build your estimated exam score.
Free to start: the study path, quizzes, flashcards and the first mock exam, no card needed. A free account keeps your place and saves your quiz scores.
