Overview

Deployments connects the work you manage in Scrambl to the releases that actually ship it. Each deployment is a record of a release into a specific environment — with a status, an optional version, and a scope: the tasks and tickets going out in it. That gives everyone, from engineers to account managers, one answer to "did that fix ship, and where?"

Turning it on

Deployments is enabled per project. In the project's settings, switch on the Deployments toggle. The project gets a Deployments tab, and a default set of environments — Development, Staging, and Production — is created the first time you use it. You can add, rename, or archive environments, set a color and URL for each, mark which one is production, and point each at the git branch it tracks.

The deployment lifecycle

StatusMeaning
PlannedCreated and being scoped; nothing has shipped.
In progress / ReadyWork is being prepared or is ready to go out.
DeployingThe rollout is running.
DeployedLive in the environment. Automations for that environment fire now.
Failed / Rolled back / CanceledTerminal outcomes that lock the scope for the record.

Scope: what is in the release

A deployment's scope is built two ways, and they combine:

  • Planned items you attach by hand while planning the release.
  • Detected items Scrambl finds automatically by comparing the code range since the last deploy to that environment against the pull requests linked to your tasks (see the CI integration article).

Where deployments show up

  • The project's Deployments tab: a table of releases with a detail panel for each — scope, environment, code range, and release notes.
  • Task and ticket details: a Deployments section lists the releases that record ships in, so status questions are answered on the record itself.
  • Client portal: individual deployments can be shared to the portal so clients see what shipped, including release notes.

Promotion between environments

When a build moves up the chain — staging to production, say — use Promote to… on a deployment. Scrambl creates a new deployment in the target environment carrying the same build, name, and version, and links it back to its source. The detail panel shows this lineage, so you can trace any production release back through the environments it passed.

Best practice: Give environments real branch names and mark production correctly. Detection baselines and automations both key off environment configuration.

Next steps

  • Wire up automatic syncing in the CI integration article.
  • Draft stakeholder-ready notes in the release notes article.