Skip to content
Confluence

Databases: View-specific field and entry ordering

Confluence databases now let each view keep its own order for fields and entries, instead of sharing one order across views. It has been rolling out to Atlassian Cloud sites since 21 Sep 2026.

  • Rolling out since 21 Sep 2026
  • Low impact

What it is

Improvement

In a Confluence database, you can arrange fields and entries separately in each view. Reordering in one view does not change the others. The database entry details experience was updated to support these view-specific orders.

Users

People working in a database can drag fields and entries into a different order in each view, and each view keeps its own arrangement.

Written from Atlassian's release note and checked against it automatically. Atlassian's original stays the source of truth.

Where the rollout is

  1. First published Done
  2. Rollout starts Done
  3. Preview track Done
  4. Bundled track Done

What changed

  1. First published by Atlassian

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

Find out what you are actually running.

Fixed scope. The assessment reads the estate as it is: instances, schemes, licensing, and the decisions a migration would force you to make anyway. You get the findings, the ownership gaps, and the order to close them in.