Confluence page suggestions on Jira Task based on key words

[Hamza Bounaim]

I'm looking for a way to automatically suggest or populate Confluence pages in Jira tasks based on title matching.

Use case: When someone creates a Jira task titled "Login performance issues", I want Jira to automatically find and display related Confluence pages (e.g., "Login troubleshooting", "Performance optimization") in the "Confluence content" field on that task.

Example:

1. User creates Jira task: "Database connection timeout"
2. Jira automatically searches Confluence for matching pages
3. Finds pages titled: "Database troubleshooting guide", "Connection pooling best practices", "Performance tuning"
4. Automatically displays these pages in the "Confluence content" field on the task (not in comments)
5. Developer can read/edit these pages directly in Jira without switching tabs

What I'm looking for:

1. Is there a built-in Jira Cloud feature that does automatic title-based matching between Jira tasks and Confluence pages?
2. Is there a Marketplace app that provides this functionality?
3. Can the "Confluence content" field be auto-populated via Jira Automation or REST API with matching Confluence pages?

Context: I used to have this feature at a previous company and I'm trying to recreate it in our current Jira Cloud instance.

[Tomislav Tobijas]

Hey @Hamza Bounaim ,

On top of what Gor said, you could try using Rovo, BUT I still don't think this will be able to create a direct link in the "Confluence content" section of the work item. 🫤

What I was thinking is to use automation + Rovo/Rovo agent to scan the summary and find related content, and then suggest or add it to the work item. Still, I think the only way would be through comments or by updating some rich text field, as automation still doesn't support populating the Confluence section of the work item: 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 👀

And as for the REST API, you can try this:

Web Link vs. Confluence Content

When you create a link via the API, Jira determines where to display it based on the globalId and relationship fields:

• Web Link: If you only provide a URL and title, Jira treats it as a generic external link and places it in the "Web links" section.

• Confluence Content: If you provide a globalId that includes a valid appId (your Confluence Application ID) and a pageId, Jira recognizes it as a native integration. This triggers the link to appear in the dedicated Confluence content section with the official Confluence icon.

Why the globalId is Critical

The globalId acts as a unique identifier that tells Jira, "This isn't just a website; it's a specific page on a trusted Atlassian application." The format must be exactly:
"globalId": "appId=<your-app-id>&pageId=<your-page-id>".

Without the appId portion of the globalId, Jira cannot verify the link against your Application Links settings, so it defaults to displaying it as a standard web link.

Summary of Requirements for the "Confluence" UI

To ensure the link populates the correct section, your POST request to /rest/api/3/issue/{issueKey}/remotelink must include:

1. globalId: Containing both appId and pageId.

2. application.type: Set to com.atlassian.confluence.

3. relationship: Set to Wiki Page.

Note: the suggestions above for REST API are purely AI-generated, so I cannot confirm that they would work

Cheers,
Tobi

[Viswanathan Ramachandran]

Hi @Hamza Bounaim 

Jira Cloud does not natively support that. You can try these marketplace apps:

• https://marketplace.atlassian.com/apps/1221971/pageify-for-jira-automate-pages
• https://deviniti.com/support/addon/cloud/advanced-confluence-integration/latest/parent-page/

or 

• Smart Links / Embedded Pages: Apps in this category display an inline Confluence preview directly inside Jira fields without requiring context switches.
• You can build a native rule via Jira Cloud Automation using a web request to search Confluence and store the matching page URLs