Automating Confluence Page Creation for Jira Product Discovery Ideas and Linked Epics

[Stephanie Ho]

I'm working on a cross-team product development setup using Jira Product Discovery and Jira Software, and I’d love some advice.

Whenever a new idea is created in JPD, I want to:

• Automatically generate a Confluence page based on a template

• Link that page to the idea

• And then, when delivery epics are linked to the idea, automatically link that same Confluence page to the epics (and ideally, back-link the page to all of them)

The goal is to have a centralized Confluence space for collaborative planning and documentation tied to the lifecycle of an initiative—from idea through delivery.

Has anyone built a workflow like this? I'm especially curious about:

• Whether it's better to trigger the automation from the idea or the epic linking

• Best practices to maintain the connection across JPD, Jira, and Confluence

• Whether ScriptRunner or native automations are more effective here

Appreciate any insights or examples—thank you!

[Marc - Devoteam · Accepted solution]

Hi @Stephanie Ho 

The options below are possible to automate.

• Automatically generate a Confluence page based on a template
• Link that page to the idea

Create an automation on the JPD project based on work item created and create a Confluence page.

The following will be harder and will require api calls (multiple) in an automation to achieve.

I can't say which ones as I have not tried this in this way.

• And then, when delivery epics are linked to the idea, automatically link that same Confluence page to the epics (and ideally, back-link the page to all of them)

[Armin Meyer _Seibert - Coderay_]

@Stephanie Ho 

I just want to add some information to Marcs answer. There are two approaches for your use case.

1) One-Time page creation with Jira Automation

Just use Jira Automation to create a page and with the help of smart values you can set jira field content into a structure you want. Creating a good looking page can be a bit of a pain.

Pros:

• It's built in and therefore cheap

Cons:

• It's a one way solution and keeping page and jira issue in sync is tricky
• Styling the page can be a pain, because you need to do it with markup

2) Use an app specialized for this use case like AutoPage or Elements Publish

Got to mention: I am part of the developement team of Autopage.

There are two specialized apps in the marketplace covering the use case.

Autopage: https://marketplace.atlassian.com/apps/1218503/autopage-create-pages-in-confluence-from-jira-issues?hosting=cloud&tab=overview

Elements Publish: https://marketplace.atlassian.com/apps/1225519/elements-publish-create-confluence-pages-from-jira-issues?tab=overview&hosting=cloud

Pros:

• Good Templating options to built good looking pages
• Sync options to keep page and jira issue content in sync

Cons

• Extra costs

Cheers

Armin

[Stephanie Ho]

The problem that I ran into was that the automations within Jira are able to create a confluence page, but because the Jira Product Discovery project a team-managed, the automation would not recognize the epics that are implemented from the the Product Discovery board. Would the marketplace apps run into this issue?