Jira <-> Confluence connecting tickets with pages via automation & API

[Spasimira Genova]

Hi everyone,

I’m trying to implement what I thought might be a somewhat doable flow in Jira Cloud + Confluence Cloud, but I’m hitting multiple issues and I can’t tell if I’m missing something obvious or if it's just the standard system limitations. I’d appreciate any guidance or “known good” patterns.

The goal is the following:

1. User opens a Jira issue in project X and clicks a rule action like “Create business case”.

2. Jira Automation creates a Confluence page using a Confluence template (we must keep the template).

3. We need a reliable link between the Jira issue and the Confluence page:

   • ideally the Jira issue link appears inside the Confluence page body, and/or

   • at minimum the Confluence page is linked back on the Jira issue.

4. (Next phase) Create different subpages under that parent "business case" page dynamically when a user in any different project (let's say project Y) opens an issue (Story) and clicks a rule action "create design review". Not sure if this is possible.

5. The idea is for this to mainly rely on the Epic parent, so another requirement was that if the Story doesn't have an Epic link, design review page creation should be blocked. Not sure if this is possible.
6. Keep a visual/structure of status pages according to the Jira tickets status. Example Page A is linked to Jira ticket A -> Jira ticket is In Progress, page also becomes In Progress, or goes to a directory for In Progress pages. Not sure if this is possible.

This is what I've tried so far:

A) Updating the Confluence page body via Send web request action to insert a link to the Jira ticket

I tried to update the created page to insert “Created from Jira: ” but I get HTTP 400 with an HTML “Bad Request” response. Even if this works, from my experience this PUT request erases the previous body of the page.

B) I also tried the remote link endpoint but nothing happens - even when I send the a request through postman and I get 201, when I open the page in Confluence no link is present.

I've left it at that for now.

My main question is does this flow sound like something that can be done at all and whether it will be worth all the complex configuration. The idea behind it is to automate documentation creation and introduce a better structure on a company level by reducing manual interventions.

Thanks in advance!

[Armin Meyer _Seibert - Coderay_]

Hi @Spasimira Genova 

I don't know if you used Jira Automation to handle the Web Request, what I would recommend. Jira Automation can handle some of these steps, the complexity of maintaining page structures and inserting Jira content often hits a wall with standard "Web Request" actions.

Here is how you can approach this:

Solving within the Atlassian Suite

You can achieve a basic version of this using Jira Automation:

• Trigger: Use a "Manual Trigger" in Jira to initiate the page creation.

• Action: Use the "Create Confluence page" action. You can select a template and insert Jira field content into the page body by using "Smart Values". 

• Linking: Automation can automatically link the created page back to the Jira issue.

• Limitations: Dynamic subpage nesting based on Epic links and automatic page status synchronization (moving pages between folders based on Jira status) are extremely difficult to maintain via native automation and often require complex scripting.

---

Solving with additional App Autopage

(!) Disclaimer: I am part of the development team and therefore biased

Autopage is designed specifically to bridge these gaps by automating the lifecycle of Confluence pages directly from Jira issues.

• Template Integration: Autopage creates pages from templates, you can design by your own, and automatically injects Jira field content (like the Issue Link, Summary, or Status) into the page body.

• Dynamic Hierarchy: You can configure Autopage to look up the Epic parent of an issue and automatically nest "Design Review" subpages under the correct "Business Case" parent page. -> HowTo for this use case

• Conditional Creation: You can set rules to ensure a page is only created if the "Epic Link" field is not empty, satisfying your requirement to block creation for orphan stories. 

• Status Syncing: As Autopage can directly insert Jira Content into a page it's easy to directly display the needed information. You can also use excerpts or page properties to have summary pages of Autopage created page trees

Try Autopage for Free: Autopage on Atlassian Marketplace 

You can also book a free demo on the Marketplace. Just let me know.

[Bill Sheboy]

Hi @Armin Meyer _Seibert - Coderay_ 

As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording, and not just in your profile name / badge. For more information, please see:

Atlassian Partners - Rules of Engagement

https://community.atlassian.com/forums/App-Central-articles/Atlassian-Partners-Rules-of-Engagement/ba-p/2899328

Additionally, please refer to the community guidelines regarding posting and attributing bot / AI-generated content:

https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement

Kind regards,
Bill

[Armin Meyer _Seibert - Coderay_]

@Bill Bill thanks for the reminder. I am part of the development team of AutoPage and I will add it in my answer.

Just to be clear about AI usage. My answer is not posted by a bot. I wrote it myself ,but I used AI to structure and to optimize my sentences, as I am not a native speaker. It's not my intention to produce AI Slop in the community. Hope this is allowed.

kind regards

Armin

[Bill Sheboy]

Thank you for that information, @Armin Meyer _Seibert - Coderay_ and if you review the community guidelines article, it describes how to use and attribute AI tools when used.