Is there a way to create Confluence pages from JIRA work item based upon a specific template?
5 answers
2 accepted
Hi @Léon Pluister ,
To add to what Anwesha said, we've implemented this simple automation so that when the work item status is changed > publish a new page with a specific template.
Now, it's far from ideal, as there are some missing elements here - at least from the automation perspective. There are a couple of feature requests you can take a look at:
- AUTO-2100: Improve Automation for Creating Confluence Pages from Jira Issues
- CONFCLOUD-80013: Improve Create Confluence Page action in A4J - automatically link the Confluence page to the Jira issue and/or be able to access the page/URL via smart values
🆕 Lately, I've been relying more on Agents in Jira for this > basically, create an agent and add it to a workflow (or add it to automation) and explain that you'd like to create a Confluence page once the work item is updated or when it reaches a specific status. You could also point it out to use a specific template (although it's not clear how stable that will be).
Anyway, I'd suggest giving it a try if you can use AI features. 👀
Cheers,
Tobi
Hi @Léon Pluister, unfortunately, there's no native way in Jira Cloud or Confluence Cloud to trigger page creation from a specific Confluence template when a Jira issue is created or updated. The closest native option is the "create Confluence page" button from Jira, but it doesn't use Confluence templates, the page is blanc.
As you've found, Rovo agents can draft content but can't be triggered by Jira events or reliably publish to a specific space from a template.
If you're open to a Marketplace app, I'd recommend AutoPage that does exactly what you're describing. You define rules in Jira that trigger on issue creation (or updates, status changes, etc.), and when a rule fires, it creates a Confluence page from a template you've set up using the normal Confluence editor. The template is just a Confluence page with AutoPage placeholder macros that pull in Jira field values - for example assignee, priority, summary, description, but also attachments (and soon comments) inline into the page content. The created page is automatically linked back to the Jira issue, and the Jira issue gets a link to the page as well.
You can scope rules to specific projects and filter by issue type or JQL conditions, so only the right issues trigger page creation. You can also set a fixed parent page or derive it dynamically from a custom field, which lets you build page trees that mirror your Jira structure.
The two sync modes are worth knowing about: "Live Update" means the Jira data on the page is retrieved in real time when someone loads the page (always current), while "On Page Update" saves a snapshot of the data at the moment the rule triggered (useful if you want a frozen record).
Full disclosure: I am affiliated with the team that build the app. But it also means I personally use it a lot and I'd be happy to answer your questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.