Can I include issue details and attachments in confluence pages created with automation ?

[Michael Mueller]

Hi there,

I know we can use the placeholders {{project.name}} and {{issue.summary}} for the page name to create the new page in confluence via automation.

Is there any possibility to copy the issue details and attachments to the automated created page as well?

That would be fantastic! 

Best regards, Michael. 

[Julien Peyrade _ Elements · Accepted solution]

Hello @Michael Mueller 

Unfortunately, this is not possible with Automation as of now.

However, if you don't mind using an add-on, Elements Publish to Confluence lets you do exactly what you are asking.

Full disclosure: I'm the Product Manager of the app.

With our app you can create Confluence pages from Jira issues. It integrates with Automation, but in addition to the native feature you can : 

• insert any Jira issue data in the Confluence page (and keep the value synchronized between the issue and the page if needed)
• use any Confluence template you need or design the page yourself
• automatically link the page to the issue
• automatically copy attachments from Jira to Confluence

The app is free for 30 days, (and stays free if your instance is under 10 users), so feel free to give it a try, and don't hesitate to tell reach our Support if you have any question.

Kind regards,

Julien

[Michael Mueller]

Dear Julien, 

many thanks .
I started testing today. And have already a big question/ issue.

I can't hide the dialog for the export in the Jira " More Options / Action menu "
It appears on any space, on any issue, even if there is no recipe set for these cases.

This will confuse other users.

How can I hide it to show it only to the allowed user group if recipie conditions are true.
Or:

hide completely if i want only fully automated exports via workflow conditions?

Best regards, Michael.

[Julien Peyrade _ Elements]

Hello @Michael Mueller 

Unfortunately, it's not possible to hide the option from this menu.

This is due to a Jira limitation : if we want to be able to offer this location to some of our users, we have to "declare" it upon the app installation. It's all or nothing for us here.

I'm sorry, I understand this can be confusing to some users.

Would another information message in the pop-up be more useful for users who click on the option by mistake?

Kind regards,

Julien

[Michael Mueller]

Thank you - hmm. cant think of another information massage atm.

Further question:
Very useful feature would be if we had if/ then options within 1 recipie.
eg:
if source project =a , then create page under parent page a1
if source project =b,  then create page under parent page a2,  etc ....

this would be the real gamechanger for me over here :-)

Best regards, Michael.

[Julien Peyrade _ Elements]

Thank you for the feedback!

I will definitively take this into consideration.

Currently, to do this, you need to create one recipe for each possible target page, and specify on which project these recipes are available in the Source tab of the recipe.