Description

In certain scenarios where Confluence templates and Jira Legacy macro are used together to create pages that list requirements encoded in Jira. These templates often contain variables for specifying Issue Key, specific labels, fix versions, etc.

However, with the transition to the cloud, these templates may not function as expected. The Jira Legacy macro in the cloud version does not allow the inclusion of template variables in the Jira search request directly on the page. Instead, users have to open the macro edit dialog. In this dialog, if a template variable is entered, it is not replaced by the variable value when the page is created. This can be a significant issue as it may disrupt the workflow of users.

The following enhancements are proposed to address this issue:

• Enable the Jira Legacy macro to support the inclusion of template variables directly on the page in the cloud version, similar to the server version.
• Ensure that the template variables entered in the macro edit dialog are replaced by their respective values when the page is created.