Releases & Environments
The Release Board tracks where your stories are in the deployment pipeline. Stories progress through environments (dev, UAT, production) and the board shows which stories have been deployed where.
Setting Up Environments
Environments are configured per repository in Project Settings, because different repos in a multi-repo project may have different deployment pipelines.
Navigate to Project Settings
Go to Project Settings > Repositories and click on the repository you want to configure.
Add environments
Add environments in deployment order. Common setups:
| Simple | Standard | Enterprise |
|---|---|---|
| dev | dev | dev |
| prod | uat | staging |
| prod | uat | |
| prod |
Configure each environment
For each environment, set:
- Name — displayed on the release board (e.g., "dev", "uat", "prod")
- Display order — determines left-to-right position on the board
- Branch mapping — the git branch this environment deploys from (e.g.,
dev,main) - Strategy —
continuous(every merge deploys) orbatched(manual release cuts) - Done target — mark one environment as the "done target." When a story is deployed here, it transitions to
done
The Release Board
The Release Board is a story-centric view. Each row is a story, each column is an environment. The cells show deployment progress.
How Dev Detection Works
For the first environment (typically dev), deployment detection is automatic:
- When a task's PR is merged, the task status moves to
mergedthendone - The release board counts tasks in
merged+ status as "deployed to dev" - Progress shows as a fraction:
3/5 taskswith a progress bar
No manual recording is needed for dev — Konductro derives it from task status.
Recording Deployments (Higher Environments)
For UAT, staging, production, and any environment beyond dev, deployments are recorded manually:
Promote stories
When a story is fully deployed at the previous environment (e.g., all tasks merged to dev), a Promote button appears on the next environment column.
Record the deployment
Click Record Deployment or the inline Promote button. Select the stories being deployed, optionally add a release label (e.g., v2.4.0) and notes.
Status transitions
When you record a deployment:
- Stories are marked as
deployedat that environment - If the environment is the done target, stories transition to
donewith timestamps - A deployment record is created for audit and history
Story Progression
Each story shows its deployment status per environment:
| State | What you see |
|---|---|
| Partial (dev only) | 3/5 with progress bar and task dots |
| Fully deployed | Green check mark with timestamp |
| Promotable | "Promote" button — story is 100% at previous env |
| Not started | Dash — story hasn't reached this environment |
Sprint Filtering
Use the filter chips to scope the release board by sprint, or select "All In-Flight" to see every story with at least one task deployed.
Deployment History
Each deployment record captures:
- Which stories and tasks were included
- Release label (if provided)
- Who triggered it and when
- Notes
This builds a natural release history that can be used for release notes and audit trails.
Multi-Repo Projects
For projects with multiple repositories, the release board shows environments per repo. Each repository has its own environment pipeline, reflecting the reality that a frontend and backend may deploy independently.
Environments are deduplicated by name in the column headers — if both repos have a "prod" environment, you see one "prod" column with status per repo.