Environments

Track where your work is deployed with environment stages. AgileTune supports manual transitions and automatic tracking from GitHub deployments.

Setting Up Environment Stages

Define the deployment pipeline for your project:

  1. Go to Project Settings → Environments
  2. Click Add Environment
  3. Enter a name (e.g., Development, Staging, Production)
  4. Set the order — stages flow from left to right
  5. Optionally add a URL for each environment (e.g., https://staging.example.com)

Common setups include:

  • Dev → Staging → Production — standard three-stage pipeline
  • Dev → QA → Staging → Production — with a dedicated QA stage
  • Preview → Production — for simpler projects

Transition Rules

Control how tasks move between environments:

  • Sequential only — tasks must pass through each stage in order
  • Skip allowed — tasks can jump directly to any stage (e.g., hotfixes to production)
  • Approval required — specific stages require approval from a designated reviewer before promotion

Configure these rules per environment in Project Settings → Environments.

Automatic Tracking from GitHub Deployments

If you've connected your GitHub repository, AgileTune can automatically update environment statuses based on GitHub deployment events:

  1. Ensure the GitHub integration is configured
  2. In Project Settings → Environments, map each AgileTune environment to a GitHub environment name
  3. When GitHub reports a successful deployment, linked tasks are automatically promoted to the matching stage

This works with any CI/CD system that creates GitHub deployments — GitHub Actions, Vercel, Railway, and others.

Environment Indicators on Tasks

Tasks display a colored badge indicating their current environment stage. This is visible on the board, in task detail views, and in list views. The badge color matches the environment color you configured.

  • Hover over the badge to see the deployment timestamp and who triggered it
  • Click the badge to view the full deployment history for that task
  • Filter the board by environment to see only tasks in a specific stage
← API ReferenceRecurring Tasks →