---
title: "About Appfire QueueZero"
canonical: "https://support.appfire.com/space/RS/3159261272/About%20Appfire%20QueueZero"
format: markdown
---
> Macro (aura-html)

Appfire QueueZero helps teams turn unresolved work items into spec-approved, review-ready pull requests.

It uses connected space context, such as work item details, repositories, documentation sources, and other approved engineering knowledge, to understand the work item, create an implementation plan, execute the plan, and open a pull request for review.

Unlike AI coding assistants that only generate code, QueueZero supports a governed workflow where teams can review plans, control execution, apply guardrails, inspect generated changes, and keep humans involved before code is merged.

![resolver-standalone-overview.mp4](media://e81dd1c3-5f00-4158-ab6e-feb94e7a3a62)

## What QueueZero includes

QueueZero has two connected apps:

> ℹ️ **Important:** QueueZero Connector for Jira requires an active QueueZero subscription. The Jira app connects to your existing QueueZero organization and cannot be used on its own. To get a subscription, refer to the Appfire listing.

## How the apps work together

The standalone app is where QueueZero is configured. Once the organization, Jira connection, QueueZero space, repository, and user access are ready, users can run QueueZero from a Jira work item.

At a high level, QueueZero works like this:

1. **[Set up the organization](https://appfire.atlassian.net/wiki/spaces/RS/pages/3293446474)**  
An organization admin creates the QueueZero organization, connects external tools, configures organization settings, and reviews billing.
2. **[Prepare the space](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166076932)**  
An organization owner or space admin creates a QueueZero space, maps it to a Jira space, adds repositories, adds documentation sources, and gives users access to the space.
3. **[Run QueueZero on a work item](https://appfire.atlassian.net/wiki/spaces/RS/pages/3159621711)**  
A developer, lead, or architect opens a Jira work item and starts QueueZero.
4. **Review the plan**  
QueueZero generates an implementation plan using the Jira work item, repository context, and connected knowledge sources.
5. **Execute the plan**  
After reviewing the plan, the user can start execution. With [single-shot resolution](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166273540), QueueZero can generate the plan and continue directly into execution.
6. **Review the pull request**  
QueueZero creates the implementation changes on a dedicated branch and opens a pull request for review. The team reviews, merges, requests changes, or continues work locally.

## Common use cases

QueueZero can help teams with work such as:

- Reducing engineering backlog and technical debt
- Resolving suitable bugs, maintenance tasks, and dependency updates
- Turning approved security or compliance issues into review-ready code changes
- Reducing manual context gathering before implementation
- Keeping AI-assisted development within defined review, approval, and guardrail workflows

## Who uses QueueZero

QueueZero has two administration levels:

- **Owners –** Owners are organization-level administrators who have access to all settings, including billing, for the entire organization.
- **Space admins – **Admins are space-level administrators with control over the knowledge and configuration used by a specific QueueZero space.

After setup, **developers, leads, and architects** can use QueueZero to generate implementation plans, execute work, review pull requests, and continue work locally when needed.

For more information, refer to **[Roles and permissions](https://appfire.atlassian.net/wiki/spaces/RS/pages/3293446483)**.

## Next step

Go to **[Get started with QueueZero](https://appfire.atlassian.net/wiki/spaces/RS/pages/3158999170)** to choose the setup path for your role.