{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/0c652cb800dd4f0fa2cc32e7e1372f02\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/0c652cb800dd4f0fa2cc32e7e1372f02-fd854e75579e3a96.gif","duration":771.826,"title":"Automated Confluence Test Coverage Pages","description":"This Loom explains how to automate Confluence test coverage report pages that reflect the current version. It shows using Confluence variables to store a version value like V. 1.0 in one shared location, then using a global template and a Confluence snapshot API key to generate the report content dynamically. The process is demonstrated by triggering a Jira manual automation, publishing a new Confluence page from the template, and then running the snapshots action to populate test coverage and test runs. The automation can be tied to relevant Jira events, and the creator noted a troubleshooting step of adding the new page reference to the audit log."}