Environments and promotion

What you’ll learn

• How environments are ordered and what a run in each one means.
• How to start a new run in the next environment.
• The difference between promoting a ticket and building it in place.
• How environment tags on Jira tickets work.

One feature, several environments

Your organisation has its environments, in order — by default Development, Staging and Production. New work is built in the first one; each later one takes over the work of the one before it. The feature's page lists every environment under Environments, with where the feature stands there.

Each environment has its own pass: its own plan, progress and Claude session. What was done in Development stays as it is when you move on.

Start a run in the next environment

When the work is done (or far enough) in Development:

1. On the feature's page, click More.
2. Choose New run in Staging (or another environment).
3. The feature moves to that environment and opens Check. You then plan and build as before.

You can also start from New feature with Move it to Staging or Release it to Production, for work already finished in the environment before.

Promote, or build here?

In Staging and Production, Claude normally promotes each ticket: it carries the finished work of the environment before over to this one, with no new code unless you ask.

To build a ticket directly in Staging or Production instead, tell Claude during Plan:

"Build APP-103 here instead of promoting it."

Claude checks your organisation's rules first — some kinds of repositories, such as shared libraries or API packages, are never built that way. Then it proposes the change for you to save, and plans again.

Example: team-invites is merged in Development. You start a new run in Staging. The plan promotes APP-101 and APP-102. APP-103 needs a Staging-only configuration change, so you ask Claude to build it there; Claude confirms the admin app allows it and re-plans.

Tickets for one environment

A ticket whose Jira title carries an environment tag belongs only to that environment:

• [test] or [development] → Development
• [stage] or [staging] → Staging
• [prod] or [production] → Production

Untagged tickets load in every environment. When you add tickets, the page shows Only loaded in Staging (for example) next to a tagged ticket. Your organisation can change these tags.

Tip: use tags for environment-specific work, such as a production data fix, so it never gets built in the wrong place.

Time logged

Each environment has a share of every ticket's estimate — by default half in Development and a quarter each in Staging and Production. The time Claude logs on commits follows that share.

Tip: an environment your organisation turned off shows Off. Features keep what was done there, but can't start new steps in it.

Check yourself

1. What does "promote" mean for a ticket in Staging?

Claude carries the finished work from Development over to Staging, with no new code unless you ask.

2. How do you build a ticket directly in Production?

Tell Claude during Plan; it checks the rules, proposes the change for you to save, and plans again.

3. A ticket's title starts with [stage]. In which environment does it load?

Only in Staging.