Skip to content
Jira

Configuration promotion from Sandbox to Production

Admins can push tested Jira and Jira Service Management configuration changes from a sandbox to production or to another linked sandbox. Atlassian marks it released in Q3 2026.

  • Released · Q3 2026
  • Open beta

What it is

Configuration Promotion moves changes such as workflows and screens from a sandbox to production or another sandbox. Admins no longer need to recreate tested changes by hand in the destination. The tool can scan a destination for differences, pick required dependencies automatically, and run validations before a deployment is finalized.

Admins

Admins can deploy configuration entities, review deployment logs, and download post-deployment reports to see the status and details of each change.

Written from Atlassian's roadmap and the release notes linked to it and checked against it automatically. Atlassian's original stays the source of truth.

What to do now

  1. Confirm that the sandbox holding your tested changes is linked to the destination environment.
  2. Identify which workflows, screens or other configuration entities you plan to promote.
  3. Scan the destination to review differences from the source before deploying.
  4. Run validations and resolve any reported errors before finalizing a deployment.

Release notes that deliver it

What changed

  1. On the roadmap when Atlas Bench began tracking it

Atlas Bench began tracking Atlassian Cloud on 29 Oct 2026. Changes before that date are not in this history.

Find out what your controls would survive.

Fixed scope. The assessment looks at permission architecture, change control, and every place audit evidence is still assembled by hand. You get the findings, the ownership gaps, and the order to close them in.