Tenant setup
Step-by-step Jira board and Augeo Forge GitHub App setup for a new Product Factory tenant.
Product Factory tenant setup
This guide is for a Jira administrator and a GitHub organization administrator on a new Product Factory tenant. Complete both procedures below before a first ticket can run. You do not need a meeting with Applied AI to match the board or to install Augeo Forge.
See What Applied AI still does after the two procedures.
The Product Factory overview explains the lifecycle these steps unlock.
What the factory keys off
The factory resolves a tenant from the ticket's Jira project key, not from the board the ticket appears on.
- One Jira project is one factory tenant mapping.
- Two boards backed by the same Jira project are not two Product Factory tenants. Adding a second board does not create a second tenant.
Match your Jira board
Copy the Applied AI board. Add the statuses and columns below with the exact names shown — character for character, including spaces and capitalization. Do not invent extra columns.
Factory workflow status names and route triggers are not the same thing as board column names. Statuses live on the project workflow and are what the factory matches. Columns are how your board displays those statuses. Keep them distinct as you work through the steps.
1. Confirm you can change the workflow
On a company-managed Jira project, adding a status usually requires Administer Jira. Project-admin permission alone is typically not enough.
If you cannot add statuses yet, skip to Fallback labels and use those until a Jira admin can finish the workflow.
2. Add the workflow statuses
Add these standard status names to the project workflow. Create transitions so a ticket can move through them in board order.
| Workflow status (exact name) | Role |
|---|---|
To Do | Starting status. |
Ready for LOE Estimation | Pointing trigger. |
Ready for Spec | Planning trigger. |
Spec Created | Plan ready for human approval. |
Ready for Agent | Implementation trigger. |
In Progress | Implementation in flight. |
Review | Draft pull request open. |
Ready for QA | Ready for human QA. |
Done | Finished work. |
These names must match exactly. Ready for LOE or Ready for agent will
not route.
Names the factory listens for
The factory routes when a ticket transitions into one of these status names. This list is the live routing table, not a second set of columns.
| Route trigger (exact status name) | What starts |
|---|---|
Ready for LOE Estimation | Pointing (complexity estimate). |
Ready for Spec | Planning. |
Ready for Agent | Implementation. |
Done | Compound (lessons after the ticket is finished). |
Optional route names a tenant may add as extra workflow statuses. They are not extra Applied AI board columns to copy:
| Optional route trigger (exact status name) | What starts |
|---|---|
Ready for Development | Implementation — same as Ready for Agent. |
Ready for Design | Design. |
If you add either optional status, map it onto an existing column from the
list below (typically Ready for Agent for Ready for Development). Do not
add a Ready for Development or Ready for Design column.
Pointing fires only on a transition into Ready for LOE Estimation.
Creating a ticket that is already in Ready for LOE Estimation does not
start pointing. Move it out and back in, or use the factory-pointing
fallback label.
3. Add the board columns
On the board for this project, add these columns in this order. Use only these eight names.
To DoReady for SpecSpec CreatedReady for AgentIn ProgressReviewReady for QADone
4. Map statuses onto those columns
A status that is not mapped to a column hides every ticket in that status from the board. Map every status you added.
| Board column | Workflow statuses in this column |
|---|---|
To Do | To Do, Ready for LOE Estimation |
Ready for Spec | Ready for Spec |
Spec Created | Spec Created |
Ready for Agent | Ready for Agent |
In Progress | In Progress |
Review | Review |
Ready for QA | Ready for QA |
Done | Done |
5. Confirm the board is not a second tenant
If this project already has a board, update that board rather than adding another. See What the factory keys off.
6. Fallback labels if you cannot add statuses yet
Until the workflow statuses exist, these labels are alternate entry points for the same stages. Add the label on the ticket (exact spelling):
| Label | Same stage as |
|---|---|
needs-spec | Transition into Ready for Spec (planning). |
factory-implement | Transition into Ready for Agent (implementation). |
factory-pointing | Transition into Ready for LOE Estimation (pointing). |
Labels are a temporary fallback. Add the statuses and column mapping when you can; the status path is the primary operator flow.
7. Verify the Jira setup
- Each standard status exists on the workflow with the exact name in the table above.
- The board shows the eight columns in the order listed, and no extra factory columns.
- Every status is mapped. A test ticket remains visible when you move it
into
Ready for LOE Estimation,Ready for Spec,Spec Created,Ready for Agent,In Progress,Review,Ready for QA, andDone. - Creating a ticket already in
Ready for LOE Estimationdoes not start pointing — only a later transition into that status (or thefactory-pointinglabel) does.
Install Augeo Forge
Augeo Forge is the existing GitHub App the factory uses to clone repositories, push spec and implementation branches, open draft pull requests, and post checks. A GitHub organization administrator installs this same app. Do not create a new GitHub App.
Listing the app on GitHub Marketplace is not required.
Kigo-Digital already has an organization-wide installation. Repositories in that organization need no second install.
Permissions on the install screen
The live app requests this complete set. Review all of them; do not treat a subset as sufficient:
- Contents write
- Pull requests write
- Checks write
- Actions read
- Metadata read
- Issues read
- Packages read
- Workflows write
Actions read is required. @augeo-forge fix loads failed workflow runs and
jobs for the pull request head. Checks write and Workflows write do not
authorize those Actions endpoints. If Actions read is missing, the fix
comments that the Actions inventory was incomplete and does not push.
The app's webhook event subscriptions come with that install. The tenant does not recreate the app and does not create those subscriptions by hand.
Install steps
- Open https://github.com/apps/augeo-forge. Do not search GitHub Marketplace for a different app, and do not register a new GitHub App.
- Choose Install (or Configure if the org already has a partial install) and select the GitHub organization that owns the repositories the factory will use.
- Choose repository access — either the whole organization or the specific repositories you will register with the factory.
- Review the permissions on the install screen. Confirm the full set listed above.
- Complete the installation.
After install, Applied AI still has to register those repositories on the factory side. The app install alone does not enroll a repo.
What Applied AI still does
A tenant admin cannot finish connection provisioning from this page. After the board matches and Augeo Forge is installed, contact the Augeo AI Acceleration team (Applied AI) for:
- Jira connection setup for your site and project key(s)
- Inbound webhook installation on your Jira site
- Repository registration and component mapping
- A secure credential handoff for the Jira service account
Do not send credentials over chat, email, or any other unsecured channel. Applied AI will arrange the handoff.
Bring your Atlassian site URL, the service-account email the factory should act as, the Jira project key(s), and each repository's GitHub slug plus the Jira component name that should route to it. The Product Factory overview lists that intake set under Becoming a tenant.