How do I insert Jira Issues into my Confluence template as part of a Jira Automation?

[Quan]

A recent update has changed the template/formatting used in Fix Version > Release Notes > Create in Confluence. This has caused a few issues as my project team and leadership prefers the original format. The new format includes too much extraneous data and fields that no one ever reads and for us, is a bit clunky. 

I am trying to update an existing Jira automation built by a colleague. creates deployment status page (parent), deployment checklist page(child) in Confluence by adding a release notes pages(child) also in Confluence as a part of the same document tree, but I'm having some trouble with Insert Jira Issue/Filter. The automation is currently able to pull the fix version name through confluence for both the deployment status and checklist page, but the release notes being a template does not want to cooperate. 

Im trying to make sure that the template pulls the version title and only the tickets relevant to the fix version payload are included(jira issue filter), but cant figure out the JQL. Im not even entirely sure this is possible to do as a template as the filtering seems to be limited to fix version IDs, which would prevent me from using {{version.name}} to filter. 

example: 

Payload 1 Fix Version: Project - 12.34.56

> after fix version is created, deployment status page and checklist page are created via automation in confluence with page titles matching the fix version/{{version.name}}

>> additional page titled Project - 12.34.56 - Release Notes is created via automation including a list of all items in the payload, ticket key, ticket type and ticket status. (this is where im having issues.

Any help is appreciated, including determining whether or not this is something that can be done in a template. 

[Humashankar VJ]

Hi @Quan 

Begin by ensuring that your Confluence template supports dynamic content insertion, as some templates may have limitations on handling Jira issue data. Verify that you're using the correct JQL query, such as filtering issues by fix version using "text fixVersion = "{{version.name}}"".

• If this doesn't work due to template constraints, consider using the fix version ID instead.
• Next, review your Jira automation rule settings to ensure that the action to create the Confluence page is correctly configured to pull in relevant fields from the Jira issues.

To troubleshoot, try using static values in your JQL to confirm that the filtering works as expected before integrating dynamic values.

Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards