Your environments

What you’ll learn

• How the order of environments decides where work is built and promoted.
• What the share of the estimate, the Jira tags and the usual branch do.
• How to add, delete, restore and turn off an environment without losing history.

Where it lives

Settings › Environments lists the environments your work moves through. Owners and admins change them; members can look. Every organisation starts with three: Development (½ of each ticket's estimate), Staging (¼) and Production (¼).

The list is used everywhere: the new-feature page, New run in…, time logged on tickets, progress pages and Claude's instructions.

Order: build first, then promote

New work is built in the first environment that is on. Each later environment promotes the work of the one before it: Staging takes Development's work, Production takes Staging's. Move an environment with ↑ and ↓.

What each environment has

• Name — what people see. Its key never changes, because features refer to it.
• On — off means no new steps there.
• Share of the estimate (%) — the part of each ticket's estimate logged there. The shares of the environments that are on can't add up to more than 100%.
• Jira title tags — for example stage, staging: a ticket whose Jira title contains [stage] or [staging] then belongs to this environment only. Type the tags without brackets.
• Usual branch — the integration branch most repositories use. Claude takes it as a hint; it is never used silently instead of the real branch.
• App address — where its app runs, shown as a link on the feature's page and given to Claude.

Time logging: your organisation decides

At the top of Settings › Environments, Time logging on Jira turns time logging on or off for the whole organisation. On, every commit Claude makes ends with #time, within each environment's share of the estimate and a daily limit per person (8 hours by default). Off, Claude adds no #time anywhere and keeps no time budget, which suits teams that don't log time, or don't allow #time in commits.

A worked example

Acme Logistics adds a QA environment between Development and Staging.

1. Click Add an environment. It appears at the end.
2. Name it QA, move it up with ↑ until it sits after Development.
3. Lower Development's Share of the estimate (%) from 50 to 40, then give QA 10, so the total stays at 100.
4. Set Jira title tags to qa and Usual branch to qa.
5. Click Save environments.

From now on, Staging promotes QA's work, and a ticket titled [qa] Fix payout rounding loads only in QA.

Tip: lower a share before raising another. The page refuses totals above 100%, so do it in that order.

Delete, restore, turn off

Delete hides an environment but keeps it, so features that used it keep their history; Restore brings it back.

If features have work in progress in an environment you turn off or delete, the page asks first and lists them. If you confirm with Yes, turn it off:

• what was done stays;
• those features can't start new steps there until it's on again;
• their owners can start a new run in another environment.

Tip: tell the owners of the listed features before you confirm. Their next step would otherwise be refused without warning.

Check yourself

1. Development is turned off. Where is new work built?

In the first environment that is on — the next one in the order.

2. A ticket's Jira title contains [staging] and Staging's tags are stage, staging. Where does it load?

In Staging only.

3. Does deleting an environment remove the history of features that used it?

No. It's hidden but kept, and can be restored.