Problem

The smart value "priorContentStatus" can't be effectively used in automation rules for Confluence because it may return empty unless the trigger is 'Page status changed'.

• This limitation hinders the ability to check the page's status from one version ago before it was edited.

{{content.status}} - the progress of a page or blog post, as indicated by the content status at the top (for example Rough draft, In progress, and Ready for review).

{{priorContentStatus}} - the previous status of the page or blog post

{{content.state}} - the publication state of the page or blog post: either Draft, Current, Archived, or Deleted

Suggested Solution

Implement an additional trigger for this smart value, or additional smart values itself as requested in CONFCLOUD-77877: Add Smart Values for page history and version for example:

{{page.previousVersion}}

Why This Is Important

Having access to a page's previous state is crucial for users to build more robust automation rules in Confluence.

This would enable users to create sophisticated workflows that depend on a page's historical status, improving efficiency and accuracy in page management.

Workaround

A workaround involves using a rule with the 'Page status changed' trigger to help another rule with the 'Page edited' trigger decide when an edit should revert the page status.

For example, the workaround may include:

• Adding a 'human-verified' label when the 'Page status changed' trigger is activated.
• Using the 'Page edited' trigger with a delay to check and remove the 'human-verified' label or change the status as needed.