Problem

In Jira automation, the "Page to edit" field of the "Edit page in Confluence" action only accepts a static page chosen from a content picker. Smart values are supported in the same action's Content field, but not in the page picker, and this applies to both project-scoped and global automation.

Proposed Solution

Allow the "Page to edit" field to accept a smart value that resolves to a Confluence page, so a single rule can target a different page depending on the work item that triggered it.

Use Case

Teams publishing release notes keep one Confluence page per Fix Version, for example "August 2026 Release". They want one rule that appends each resolved work item to the page matching its Fix Version, but today they must either create a separate rule for every release page or replace the action with a Send web request implementation against the Confluence REST API.