You shouldn’t have to hunt through a cluttered dashboard to understand where your code is deployed. The Deployments page is where teams turn for a quick answer: what is in test, what is in staging, what reached production, and what needs attention right now. The older page made that harder than it needed to be.

Our new Pipelines Deployments page makes it easier to scan, filter, and act on. The new experience organizes environments clearly, surfaces the most important deployment details in one place, and updates live as pipelines run.

What this improves for your team

The previous Deployments page was functional, but required too much cognitive load. This refresh solves these day-to-day usability problems without changing core deployment concepts:

  • Faster way to narrow results: The new experience puts powerful filtering front and center, so you can zero in on exactly what you need without scrolling or manual searching.
  • Easier-to-scan layouts: Deployment information is now visually organized so comparing environments feels effortless, not overwhelming.
  • Full deployment history: Environment history is now prominently surfaced and easy to access, so nothing important gets buried or missed.

What’s new

A cleaner, column-based layout

Environments are grouped into clear Test, Staging, and Production columns. The relationship between environment type and individual environments is understandable at a glance. Columns keep their structure even when empty, so the overall page remains predictable and easy to scan

Filters that help you get to the answer faster

Narrow the page results using combined filters to isolate exactly what you need:

  • Author to focus on deployments associated with a specific commit author
  • Environment name to quickly find the environment you care about
  • Status to jump straight to failures, paused runs, or deployments in progress

Richer deployment cards

Each environment uses a single, redesigned card bringing the most useful information into one place. Users can quickly see:

  • Deployment status
  • Environment name
  • Build number
  • Commit hash and message
  • Commit author
  • Time

History that is easier to discover

Deployment history is explicitly accessible from within each card. The history panel opens alongside the main page, allowing you to inspect recent deployments for an environment without losing context.

Live updates as pipelines run

The page updates in real-time as deployment events happen. When a deployment starts, changes status, or completes, the page reflects that automatically without requiring a browser refresh.

What’s next

Future updates will focus on moving teams from deployment status to action more quickly. We’re exploring adding links to runbooks and operational tools such as Splunk, to help you reduce context switching.

Not using Deployments yet? Give it a try

If your team isn’t already utilizing Bitbucket Pipelines for deployments yet, you can get started today.

Here is a sample bitbucket-pipelines.yml configuration that triggers deployments against the relevant production environment:

image: atlassian/default-image:5
pipelines:
  branches:
    main:
      - step:
          name: Deploy to production
          deployment: production
          script:
            - echo "Deploying to production"

Have feedback?

Share your feedback to help prioritize what comes next for Deployments. Join the conversation on the Atlassian Community page, review the support docs, or reach out to the support team.