Inline Macro:
This macro is suitable for most content. The Jira content will be placed inline, exactly where you position the macro.
AutoPage templates are simple Confluence pages that act as blueprints for creating new pages with content from Jira issues. The “magic” happens with AutoPage placeholder macros, which define where Jira content should be inserted.
You can create your template page in any Confluence space and give it any name. However, it’s a good idea to establish a naming and storage convention for your templates. This makes them easier to find when configuring AutoPage rules and helps users understand their purpose.
Space Selection:
Naming Convention: We recommend using the prefix “AutoPage Template -” followed by the type of documentation (e.g., “AutoPage Template - EPIC Documentation” or “AutoPage Template - Project Summary”).
Edit your template page just like any other Confluence page. The key difference is that you’ll use AutoPage macros to define how and what Jira issue content is inserted.
To insert an AutoPage macro:
Type /Autopage
or click the +
icon in the editor menu.
You can customize your page after it’s created by AutoPage. You can even add macros to a page after it’s generated for more flexibility.
There are three types of AutoPage macros for inserting content from Jira into your Confluence pages:
Inline Macro:
This macro is suitable for most content. The Jira content will be placed inline, exactly where you position the macro.
Card Macro
Use this macro to insert rich text content from Jira, such as Description fields or Multiline Custom Fields. The content will be placed as a block of text between two rows on your page.
Rich Text Macro
This macro displays the connected Jira Issue as a card. You can choose from three display modes: small, medium, or large.
AutoPage macros currently support the following Jira custom field types:
Field Type | Macro Type | Advanced Formatting |
---|---|---|
Paragraph (rich text, multi-line, issue description) | Rich Text (Block) | Styling is inherited from Jira |
Date / DateTime | Inline | Formatting predefined |
Text field / Short Text (single-line) | Inline | Formatting can be defined |
Number field | Inline | Formatting predefined |
User / User Picker (single user, multiple users) | Inline | Formatting predefined |
Project / Project Picker | Inline | Formatting predefined |
Issue status | Inline | Formatting predefined |
Issue priority | Inline | Formatting predefined |
Issue type | Inline | Formatting predefined |
Votes | Inline | Formatting predefined |
Labels | Inline | Formatting predefined |
Version / Version Picker | Inline | Formatting predefined |
Components | Inline | Formatting predefined |
Select List | Inline | Formatting predefined |
Radio Buttons | Inline | Formatting predefined |
Sprint | Inline | Formatting predefined |
More field types coming soon: Issuelinks & Parent, Time tracking fields, Service Desk fields.
Once you’ve inserted a macro, you’ll need to configure its details. Click on the Macro Placeholder in the page edit mode, then click the “pen icon” to open the configuration menu.
The configuration menu will appear on the right side, where you can choose the Jira custom field you want to display.
You can choose between two sync modes for your macros:
“Live Update” (Default Setting): The content of the configured Jira custom field is retrieved in real-time when you load the Confluence page. This ensures users see the latest Jira changes, but it may result in slower performance and no data displayed if communication with the Jira API fails.
“On Page Update”: This mode saves the Jira issue content directly into the Confluence page when the AutoPage rule is triggered. Users will see a snapshot of the Jira issue from that specific point in time. This offers faster loading performance, and content will still be shown even if Jira is temporarily unavailable.
For Inline Macros with text information, you can define the display mode (refer to the “Supported Jira Field Types” table above for details).