---
title: "Set up spaces"
canonical: "https://support.appfire.com/space/RS/3166076932/Set%20up%20spaces"
format: markdown
---
> Macro (aura-html)

Use **Spaces** to create and manage Appfire QueueZero spaces.

QueueZero space administration includes connecting Jira work to a QueueZero space, configuring space-specific settings, managing members, and setting up repositories and other knowledge used during planning and execution.

> ℹ️ For example, you might create one QueueZero space for:
> ℹ️ 
> ℹ️ - A Jira work area and its main application repository.
> ℹ️ - A product area that uses multiple repositories.
> ℹ️ - A team that works from one shared Jira backlog.
> ℹ️ - A group of services that are often updated together.

## Space setup flow

### Step 1: Create a QueueZero space

1. Open the QueueZero app.
2. From the side menu, select **Spaces**.
3. Click **New space**.
4. From the search field, enter a Jira space key or space name.
5. Select your Jira space from the list.   
:note: A QueueZero space inherits its space names and space keys from the Jira space to which it is linked.
6. After the Jira space is mapped, its work items will appear in the QueueZero space.

### Step 2: Set up space knowledge

Use the **Settings** > **Knowledge** tab to add the code and documentation QueueZero uses during planning and execution. A knowledge source can include:

- A repository
- A tracked branch
- A code graph
- Documentation links

You can add documentation sources when QueueZero needs context that may not be clear from code alone, such as business rules, architecture notes, product behavior, or team processes.

1. Open the QueueZero space.
2. Select **Settings**.
3. Open the **Knowledge** tab.
4. Click **Add Repository**.
5. Choose **GitHub** or **Bitbucket**.
6. Select a repository, or enter a repository URL manually.
7. Optionally, add a Confluence documentation URL.
8. Set the max documentation depth, which is the number of levels to crawl from the root page (0 = root page only).
9. Click **Add Repository**.

After the repository is added, it appears under **Knowledge Sources**. Expand it to view further actions.

![admin-SpaceSettingsKnowledgeTab.png](media://f61f4ca0-10b3-4766-8e57-53313bd584cc)

#### 1. Review the tracked branch

Each repository has a tracked branch. QueueZero uses this branch when indexing space context. To use a different branch, select **Change branch** and choose the branch QueueZero should track.

#### 2. Set up Environment

An environment lets QueueZero run your repository's install, lint, and test commands in an isolated VM so it can verify changes against the repository before creating a pull request. This is referred to as **Env Grounding**.

Env Grounding is configured separately for each repository. Expand a repository under **Settings > Knowledge** and use the **Environment** card to enable and configure it.

For setup instructions and information about verification results, see **[Set up Env Grounding](https://appfire.atlassian.net/wiki/spaces/RS/pages/3624304708)**.

#### 3. Index the code graph

The code graph helps QueueZero understand repository structure and code relationships.

The **Code Graph** card shows the current indexing status. If the code graph is not indexed or needs to be updated, select **Re-index**. 

To re-index all knowledge sources in the space, click **Re-index All**.

#### 4. Link documentation

One or more Confluence spaces can be added to a space. Confluence spaces can provide additional context including business rules, feature documentation, PRDs, and more. Click **Manage links** to add or remove documentation links. 

### Step 4: Check that space setup is complete

Before handing off to developers, confirm that:

- at least one repository is added,
- at least one knowledge source is added,
- indexing completed successfully,
- Env Grounding is configured for repositories where environment verification is required,
- the space is ready for plan generation.

A developer should then be able to:

- open a Jira work item,
- open QueueZero,
- review or adjust the suggested repository selection,
- review the branch configuration,
- start a resolution.