Confluence automation with Page Properties

[cosmin_parnia]

Hi everyone,

I am trying to build a confluence automation as following:

• Trigger: page published
• Condition: a template is used
• Action: create a Jira ticket. It needs to contain:
  • Summary
  • Reporter
  • DueDate

In the confluence page that is used, I use the Page Properties Macro, with hope to automate the fields above.

I use the content properties macro horizontally. Column 1 is the header, column 2 has the data.

I then used these properties to auto-fill the data in the Jira ticket, as following:

• Summary = {{page.properties.Title}}
• Reporter = {{page.properties.Reporter.accountId}}
• DueDate = {{page.properties.Date}}

I used action log to see if data is read properly, but the logs are empty.

Then I decided to use {{page.body.storage}} to see how the storage is structured.

But I was very surprised to find out that instead of 

• <ac:structured-macro ac:name="page-properties"

I get

• <ac:structured-macro ac:name="details"

and my understanding is that these are 2 different macros. 

In this case it makes sense why all my audit logs are empty, but why it shows as I am using "details" macro if I added "page-properties".

Thank you!!

[Tomislav Tobijas · Accepted solution]

Hi @cosmin_parnia ,

It seems that's the background macro name (probably some old entity).

Anyway, this is a bit tricky as you'll have to parse content, as you've noticed, to get values such as Summary, Reporter, and Due date from the page and store those in Jira items.

This might give you some insights and ideas on how to do so, but you'll probably have to play around to extract what you want: https://community.atlassian.com/forums/Confluence-questions/Email-recipients-based-on-Page-properties-smart-values/qaa-p/2903295#M330368

Cheers,
Tobi

[cosmin_parnia]

Hi @Tomislav Tobijas

Thank you for the solution!

It partially worked so far, but I need to play with it a bit more for the rest of the values.

Indeed, the naming convention might be coming from the old editor, and it's frustrating that Atlassian cannot be always consistent, but so be it :)

Thank you again Tobias!

[Jad Saliba]

Hi @cosmin_parnia ,

As @Tomislav Tobijas already mentioned, you are not the first person to try to implement something like this.
Given how awkward it is to parse content properties, we are wondering if there is interest in a marketplace app that does the parsing for you?

This could be something like a custom automation action similar to “Create Variable“ that automatically creates variables for all Content Properties on a given page. You would then be able to use these variables in all down-stream actions.

The idea is still in it’s very early stages. We would be very much interested in your thoughts.
Could you see yourself benefiting from something like this?

Cheers!
Jad

Disclaimer: I am affiliated with TNG Technology Consulting GmbH, an Atlassian Marketplace Partner