Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Publishing byline
...
state and page changes
A source space page and the published page of 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 state and will cause a
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
A page may need to be refreshed after the change to display the updated publishing status state byline.
User action | Sets publishing status state as: | Notes | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Edit a page (in either source space or target space) |
| |||||||||||||||
Move a page in the source space that includes a change in the hierarchy |
|
| ||||||||||||||
Move a page in the target space that includes a change in the hierarchy |
|
| ||||||||||||||
Add label
|
| |||||||||||||||
Remove label
|
| |||||||||||||||
Add attachment
|
| |||||||||||||||
Delete attachment
|
| |||||||||||||||
Check /or uncheck the box for any macro, for example, task macro
|
| Multiple changes in a macro in a short period of 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 the 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
| ||||||||||||||
Archive published page in the target space | If the page is archived in the target space
| An edit to the source space page whilst , while the target space page is archived will cause , causes the publishing status state to be
| ||||||||||||||
Delete a published and synced page from the 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 the target space | If the 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 state at the time of deletion (if there has have been no changes to the target space page) and the The publishing 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 have been no changes to the source space page). The source space page retains the
|
If a new page has been created by a publish action, restoring the deleted page in the target space trash will offer two options
| ||||||||||||||
* 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. |
Info |
---|
A user viewing a page does not cause any change in the publishing statusstate. |
Tip |
---|
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. |
...