Hello,
I am trying to automate release documentation in Confluence based on Jira FixVersion events.
Currently Jira Versions aka Releases are created and maintained in Jira projects. For audit purposes we need to maintain release overview pages in Confluence as well.
My goal is to eliminate the manual updating of those confluence lists.
What already works:
Using Jira Automation's "Edit page in Confluence" action, I can:
- update existing Confluence pages
- insert tables
- resolve Smart Values such as {{version.name}}{{version.id}}{{version.description}}{{version.releaseDate}}{{now}}
However, this only appends/extents the page but it's not "smart" in the sense that it works in one table on the confluence page and updates it. So the flow should look like this for example
- Trigger in Jira project (Release Created, Updated or Deleted).
- Reads existing Confluence page content
- Finds a release entry by a unique identifier (e.g. Jira Version ID)
- Updates that entry instead of appending new content
Has anyone implemented something like this without using an external system such as Power Automate, ScriptRunner or Forge?
Any examples or best practices would be greatly appreciated!
I added a screenshot of an example how the table could look like in Confluence.