Publishing byline status and page changes
A source space page and the target space published page will remain in sync until a user action triggers an Atlassian page update event.
User actions on a published and synced page
The following user actions on a published page in either the source or target space affect the publishing status and will cause a SYNCED page to move to a move to a different publishing status, such asOUT OF SYNC.
A page may need to be refreshed after the change to display the updated publishing status byline.
User action | Sets publishing status as | Notes |
|---|---|---|
Edit a page (in either source space or target space) | OUT OF SYNC | |
Move a page in the source space that includes a change in the hierarchy | OUT OF SYNC |
|
Move a page in the target space that includes a change in the hierarchy | NO CHANGE IN STATUS |
|
Add label
| OUT OF SYNC | |
Remove label
| OUT OF SYNC | |
Add attachment
| OUT OF SYNC | |
Delete attachment
| OUT OF SYNC | |
Check/uncheck box for any macro, for example, task macro
| OUT OF SYNC | Multiple changes in a macro in a short period time, for example checking several tasks as completed, may only cause one Confluence update as Confluence Cloud may process these changes in a batch process. |
Archive published page in the source space | If page is archived in the source space
| Any edits to the target space page whilst the source space page is archived will cause the publishing status on the target space page to be OUT OF SYNC. Restoring a page from the archive sets the publishing status to OUT OF SYNC on each page and enables the page to be published and synced from the source space. |
Archive published page in the target space | If page is archived in the target space
| An edit to the source space page whilst the target space page is archived will cause the publishing status to be OUT OF SYNC on the source space page. Restoring a page from the archive sets the publishing status to OUT OF SYNC on each page and enables the page to be published and synced from the source space. |
Delete published and synced page from source space | If a previously published page is deleted from the source space
 | Publishing the source space page creates a new page even if the deleted target space page has been ‘restored from trash’.* |
Delete published and synced page from target space | If page is deleted from the target space
| |
Restored page from source space Trash
| A ‘restored from trash’ source space page will be restored with the publishing status at the time of deletion (if there has been no changes to the target space page) and the popup will include a link to the target space page. | |
Restored page from target space Trash
| A ‘restored from trash’ target space page is restored with the publishing status at the time of deletion (if there has been no changes to the source space page). The source space page retains the NEW publishing status until a new publishing action. | If the archived target space page has not been restored, any publishing action on the source space page will create a new page in the target space.* If a new page has been created by a publish action, restoring the deleted page in the target space trash will offer two options
Restoring a page from trash may restore the page to the root of the space. |
* Publishing to a target space with an existing page that has the same page title as a source space page may cause publishing problems. You may need to rename pages or remove pages before publishing. | ||
A user viewing a page does not cause any change in the publishing status.
Atlassian update events related to some of these user actions do not necessarily increment the Confluence version of the source space page, but a publishing action will increment the target space page Confluence version. For example, adding a label does not increment the page version in a source space, but publishing this change will increment the target space version.