Add a "Page moved" trigger to auto-start rules
Description
Problem
Auto-start rules in Approval Path for Confluence start an approval only when a page is created or a label is added. A page moved to another space or under another parent where a rule applies (for example a condition ancestor = 123) gets no approval. The admin has to start it manually or through a bulk run.
Change
-
The rule form has a new trigger "Page moved", off by default.
-
Moving a page to a space or under a parent that matches the rule's scope and CQL condition runs the rule the same way as the other triggers.
-
A move within the same space also counts (parent change).
-
The approval initiator is the person who moved the page, with the same fallback user as for the other triggers.
-
"Test on page" and the Run log show the "Page moved" trigger.
Out of scope
-
Moving to trash, restoring from trash, copying a page.
-
Approvals that already exist on the moved page (their space is updated as today).
Acceptance criteria
-
A page moved to a space covered by a rule with the "Page moved" trigger gets an approval of the rule's definition.
-
A page moved under a parent that matches the rule's
ancestorcondition gets an approval, also when the move stays within the same space. -
A rule without the "Page moved" trigger does not react to a move.
-
A page that already has an in-progress or valid approval of the same definition does not get a second one.
-
The approval initiator is the person who moved the page.
-
The Run log records the decision with the "Page moved" trigger.