Can I create detailed Confluence pages using Jira Automation?

[Mike Clarke]

Hi,

When a Problem is closed as a Known Error in JSM, I want to create a Known Error Report in Confluence, and copy across relevant information from some of the Jira fields e.g. "Root Cause" and "Workaround" if they have values in them.

So I've configured an automation rule in JSM that creates a Confluence space for all Problems that get transitioned to the status Completed with the Resolution set to Known Error.
I've connected Confluence to the Rule, selected the appropriate Space and Parent Page, but for some reason the ITSM Known Errors template is unavailable?

Also, how do I get the Confluence Page to pull field values from the trigger Jira issue?

e.g. the highlighted items should get populated with the appropriate fields from the trigger issue.

The idea being that if Known Error Reports need to be shared, the Confluence Page can be designed in a way that only exposes the information that is appropriate to be shared, can be shared with Guests etc or exported as a PDF, and is a bit "glossier" than a Jira issue view.

Has anyone done something like this before? 

[Charlie Misonne · Accepted solution]

Hi Mike,

I'm not sure why the ITSM Known Errors are not showing up. But I think you can only pick space templates you made yourself. It does not show the full list of templates provided by Atlassian out of the box.

For your other question: the Jira Automation - Confluence is very basic at the moment. It can create a page but it can not set the content of the page. Here is a related feature request: https://jira.atlassian.com/browse/AUTO-82

We decided not to use the Confluence actions. We use the Send web request instead. This allows us to use the Confluence REST API. In the http request's payload we send the page's content in storage format. This is the XML representation of the page. In the XML you can use any automation smart values.
If you need more details let me know.

[Mike Clarke]

Hi @Charlie Misonne 

Thanks for the post.  This looks like it'll be the way we'll need to lean to fulfil the "no add-ons" requirement.
I've not had much experience in working with APIs so will need to study up, but at least I've got a good target to learn towards now.

Thanks

Mike

[Charlie Misonne]

You're welcome!

and good luck with your setup

[Thibaut Subra _Elements_]

Hi @Mike Clarke 

If using a third-party app is an option for you, I suggest taking a look at our application Publish.

It allows you to publish custom pages (with custom templates or Confluence templates) from Jira to Confluence by retrieving values (fields, attachments, comments, etc.) from an issue as well as its parent and soon its children. That way, you choose exactly what you want to publish and what your page will look like.

You can also trigger your recipe directly from Automation in your case.

You can take a look at our documentation to have an overview of how it works, but I'll be glad to help if needed.

Regards

Thibaut

[Mike Clarke]

Hi @Thibaut Subra _Elements_  

Your add-on sounds like exactly what we'd need which is fantastic, and frustrating all at once.

The requirements I've been given are to exclude 3rd Party Apps from the solution, but I'll make the case that using your add-on will require less build costs, and lower maintenance overhead

Thanks

Mike