Confluence Templates
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.
Getting Started: Create Your Template Page
Section titled “Getting Started: Create Your Template Page”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:
- If a template will only be used within a specific space, create it directly in that space.
- For templates used across multiple spaces, choose a more general space.
-
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”).
Style Your Page with AutoPage Macros
Section titled “Style Your Page with AutoPage Macros”Edit your template page just like any other Confluence page. The key difference is that in order to create a Confluence page from a template, you’ll use AutoPage macros to define how and what Jira issue content is inserted.
Who can see macro content
Section titled “Who can see macro content”Two independent things determine whether a user sees the content of an AutoPage macro:
- Jira product access (licence) — A user without access to Jira does not see the Jira content. The macro displays a message in its place instead of rendering the content. This applies to every AutoPage macro type.
- Jira project and issue permissions — These are not evaluated. A licensed Jira user who would not be able to open the work item in Jira still sees the content rendered by the macro.
To restrict who can see macro content, apply Confluence page-level permissions to the generated page.
To insert an AutoPage macro:
Type /Autopage or click the + icon in the editor menu.
To configure a macro: Click the Macro Placeholder in the page edit mode, then click the “pen icon” to open the configuration panel on the right side. The available configuration options depend on the macro type — see the individual macro pages below.
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.
AutoPage Macro Types
Section titled “AutoPage Macro Types”There are five types of AutoPage macros for inserting content from Jira into your Confluence pages:
Supported Jira Field Types
Section titled “Supported Jira Field Types”AutoPage macros currently support the following Jira 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 |
| AgileHive Custom Fields | Inline | Formatting predefined |
| Issue links / Subtasks | Linked Issues | Layout and link type filter configurable |
| Attachments | Attachments | Layout, display fields and sort order configurable |
More field types coming soon: Parent, Time tracking fields, Service Desk fields.
Macro Sync Mode
Section titled “Macro Sync Mode”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 a real-time Jira Confluence integration (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.
The rule is triggered by a Jira event — for example when the linked work item is created or updated. Editing and saving the Confluence page does not refresh the snapshot, and there is no manual refresh action on the page. If a macro should always show current Jira data, use “Live Update” instead.