We've launched an upgraded Publish New Page action in Jira Automation

[#1]

 Hi Community! Mehak from Automation Platform here with an exciting announcement on a new action component. We have launched an upgraded ‘Publish new page in Confluence' action in Jira and are replacing any existing rules that use the old ‘Create Page in Confluence’ action with the new one.

Based on customer demand, this improved action will mirror the capabilities of the 'Publish new page in Confluence' action we currently have in Confluence.

This means, like the action in Confluence, the new action in Jira will allow you to:

• Configure page content

• Pick from a wider variety of templates

• Pick a template from a different space than your created page

This increased capability will allow you to:

• Publish release notes when a Jira sprint ends

• Use a Rovo agent to publish a Confluence page

• and so much more!

What will this look like?

Just like the old action, this will be accessible as an action within rule builder however with additional fields; template, template space and page content.

Here is what it will look like:

When will it be rolled out?

We have already replaced the old action, so the new action is now accessible to all Jira Cloud Free, Standard, Premium and Enterprise customers.

What happens to the old action?

The old action will still be available on existing rules, but can no longer be added to new rules. Existing rules will still run, however you’ll see an option to switch to the new action.

Here is what the messaging on the action will look like:

As we roll out, we will switch your rules over to the new action. We will keep you posted on when this is complete. 

We hope you enjoy the new action and all the new capabilities it unlocks!

We want to hear from you

Have any questions or feedback? We’d love to hear from you, so please don’t hesitate to schedule time with us directly or leave a comment on this post.

[Bill Sheboy]

Hi @Mehak Bokhari 

Thanks for this great addition to rule actions!  This may save people an additional call to the REST API to update the content of newly created pages.

On the topic of content, what will be accepted in the Page Content field: plain text, HTML, markup, the same raw content as for the REST API endpoint, etc.?

Kind regards,
Bill

[Bill Sheboy]

Greetings, community!

After no responses to my above question about what Page Content information will work with the new action, I experimented and observed the following:

• the field accepts plain text
• the field accepts bullet / list markup, such as with * a bullet here
• table markup does not work; for example:

||heading 1||heading 2||heading 3||
|col A1|col A2|col A3|
|col B1|col B2|col B3|

• HTML does not work
• using the Confluence macro / markup directly from a working page's storage, such as from a REST API response, does not work

Short answer: this feature works for basic text and if you need more extensive formatting, continue to use a direct call to the REST API endpoint to update the page's storage / content.

Thanks!

[Mehak Bokhari]

Hi @Bill Sheboy

Sorry for the delay in response and thank you for your explanation above. You are correct in the above message, this action supports plain text. 

In saying this, I would love to hear from you what other formats would be helpful and if there were any particular use cases you had in mind for these formats. This would be something the team can explore to improve the current action or similar actions.

Alternatively, if there's any other questions or feedback, feel free to book in some time here so we can chat 😃

Cheers,

Mehak

[Bill Sheboy]

Hi @Mehak Bokhari 

If you search community questions / posts, you will find examples where people create a page with the old action (perhaps using a template), and then call the REST API endpoint to read the content storage and use text functions to make a modification...followed by another endpoint call for the update.  Those are often experiment-based exercises to learn and modify the page macros in the raw storage.  Examples include:

• toggling task completion
• adding / modifying tasks
• managing approval workflow
• creating static page content to reflect a point-in-time report of some Jira work items
• etc.

I am honestly not clear how one could workaround that for Confluence page macros / formatting as the simple text box fields in the rule editor are not conducive to any form of non-trivial formatting.  For example, even to update the Description field of a Jira work item one must use the REST API to send the ADF format when it contains macros!

Perhaps a start would be to accept all of the basic markup syntax, translating that behind the scenes into appropriate Confluence page content: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all  Then perhaps adding the ability to update / replace the content storage using macros.

Thanks again!