Unable to Select Confluence Space in Jira Automation "Publish New Page" Action

Hi @cvanduyn, if that flow is scoped to a single project, this is AUTO-2415, raised on 22 July. The space picker in a project-scoped rule sends your Jira project id where a Confluence space query belongs, so nothing comes back to list. That fits the Connected status and the No space found across the projects you tried.

Rebuild the same action under Global Automation to confirm it. Spaces populate there, and that's the way around it too. Build the rule in the project with everything except that action, open it from Global Automation, switch the scope from Single project to Global, pick the space, then set the scope back and save. The space survives the switch.

@Jose Carlos Gomez, the ticket already has six votes and fifteen watchers, so you've got company.

https://jira.atlassian.com/browse/AUTO-2415

Hi @cvanduyn

Hi @cvanduyn!

This is a classic and quite frustrating scenario where "Connected" doesn't necessarily mean "Authorized."

In Atlassian's ecosystem, the Connected status in the automation settings usually confirms that the OAuth handshake or API token authentication was successful (i.e., the system knows who you are). However, the empty dropdown in the "Publish New Page" action is an authorization issue (i.e., the system doesn't think you have the right to do anything in those spaces).

Here is a checklist to narrow this down:

1. Verify Space-Level Permissions: Ensure that the exact account used to establish the connection has the 'Create Page' permission in the target Confluence spaces. If the user can't manually create a page in that space, the automation won't see it.

2. Test with a Space Admin: To rule out a bug in the AI agent/Automation flow, try creating a temporary connection using a Confluence Space Administrator account. If the spaces suddenly appear, you know it's a granular permission issue with the original account.

3. Global Permissions: Check if the account has the global permission to use Confluence. Sometimes, a user might have access to a space but lack the broader permission to interact with the Confluence API.

4. The "New Feature" Factor: Since you mentioned this involves the newer AI agent features, there might be a specific "App" or "Bot" user created in the background. Check the User Management in Confluence to see if any automation-related service accounts have been created and if they are added to the space permissions.

Pro Tip: If you have access to the browser's Developer Tools (Network tab), try clicking that dropdown and look for the API call to /wiki/rest/api/space. If you see a 403 Forbidden or an empty array [] in the response, it confirms that the API is rejecting the request based on permissions, not a connection failure.

Hope this helps you get those pages publishing! 🚀

Hi @cvanduyn

As an alternative to Automation, you could try our app Elements Publish instead.

It's built for this exact use case: you can automatically create a Confluence page from a Jira issue and insert any field directly into the page, including inside a Confluence template body (something Automation currently can't do, it only supports smart values in the page title).

Another advantage: Elements Publish can keep the Jira issue and Confluence page synchronized, so every time a field is updated in Jira, the Confluence page stays up to date automatically.

You can check the documentation here if you want to take a look. Also, don't hesitate to try the app, it's free for 30 days (and stays free under 10 users).