Skip to main content
Skip table of contents

Mandatory update of Elements Publish for Child Issues

This update is mandatory for using of Elements Publish for Child Issues macro content in Confluence Templates.

Purpose

This documentation explains how to make Elements Publish for Child Issues macro work again when included Confluence templates used in Elements Publish recipes.

  • Scope: Applies to all Publish recipes that use a Confluence template including an Elements Publish for Child Issues macro.

  • Audience: Jira and Confluence administrators.

Before You Begin

Before executing migration procedure

  • End users will encounter an error message while executing Publish recipe

image-20250831-184221.png
  • Administrators will see an error log inside Logs section of Publish administration

To resolve this, administrators must follow the migration procedure described below.

Migration Procedure

  1. Open Elements Publish Administration

    • Navigate to the recipe section.

  2. Edit the Recipe

    • Select and edit the related recipe.

  3. Access the Content Section

    • Go to the Content section.

    • Once the page loads, click the Edit template button.

      edit-template.png
  1. Open the Template in Confluence

    • You will be redirected to the edit mode of the corresponding template in Confluence.

    • Locate the Elements Publish for Child Issues macro in the page content.

    • Select the macro and click Edit.

      image-20250901-091321.png
  1. Review and Save Macro Content

    • A Confluence editor will open in a popup containing the macro content.

    • If the Save button is disabled, enter a space at the end to update the content and enable saving.

    • Click Save at the bottom of the popup.

      image-20250901-091346.png
  2. Save Confluence template

Completion

Once the macro content is saved, the migration process is complete.
Repeat these steps for each Publish recipe that includes a Publish for Child Issues macro.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.