Want to create Epics in Jira when Lean Business Case in Confluence is approved.

[Julie Mason]

Hi there,

We currently have product owners using a Lean Business Case form in Confluence for analysis-gathering. We'd like to have a trigger that generates an Epic in Jira when the LBC is approved for development. I don't see a way to create custom variables to enable pulling the summary, description and reporter for creating the issue. Does anyone know if this can be accomplished with Confluence automation?

Thanks!

[Martin Runge]

Hi @Julie Mason

Confluence automation itself cannot parse individual sections out of a page body, so pulling a clean summary, description and reporter from the LBC form is the wall you are hitting. 

Two routes I would consider.

• Simple route, no AI. Add a label like "approved-for-dev" on the LBC when it is signed off. Then build a rule with trigger Label added and action Create Jira issue, mapping Summary to {{page.title}} and Description to {{page.url}}. Clean and deterministic, but the Epic gets a link back rather than the case text.

• Rovo route, when you really need the text parsed. Same trigger, but add a Use Rovo action that reads the page and returns the summary and description as JSON. Then feed that into Create Jira issue using {{jsonStringToObject(rovoResponse).summary}} and so on. Tell it to return raw JSON with no code fences or parsing breaks, and do not trust it for the page link; use {{page.url}} instead.

The reporter faces difficulty because the PO approval isn't transparent. How approval is recorded—manual sign-off, page status, or an app like Comala—determines the recommended trigger.

Cheers, Martin