Creating Confluence page and Jira Epics when an idea transitions

[Deepa Pai]

Hi There

Im tryign to automate the creation of artefacts needed to deliver an idea when it transitions from one status to the next in JPD. e.g Idea goes from Discovery to Definition status. At this point, I want a 3-4 documents created in Confluence based off the information in the idea ticket. I can see the rule being executed and the transition being picked up. However no confluence page is not created. I can see the No Actions Performed. How do I know if the cuase of this issue, how can I investigate further to determine if its permission or something else?

[Ajay _view26_]

Hi @Deepa Pai 

If the rule is triggering but the audit log says “No actions performed”, I’d first check whether the action conditions are actually matching and whether the automation actor has access to both the target Jira project and the Confluence space.

A couple of important things from Atlassian’s docs:
- the “Create Confluence page” action can create the page title, but it does not create page content
- it requires a working Jira-to-Confluence connection
- if you want to link the created page back to the idea/work item, you can use the created page smart values such as {{createdPage.url}} in a later step

So I’d verify:
1. the automation actor can create pages in the target Confluence space
2. the Jira Product Discovery space is actually connected to the intended Confluence site/space
3. there isn’t an if/else or branch condition causing the action to be skipped
4. you’re not expecting the Create Confluence page action to populate the page body automatically

If the audit log still only shows “No actions performed”, I’d simplify the rule to just:
- trigger on status change
- create one Confluence page with a static title
- create one Epic in the target project

If that works, then add the dynamic fields back one by one. That usually makes it easier to tell whether the problem is permissions, branching, or a field/smart value issue.