Skip to content

Jira Rules

AutoPage streamlines documentation by keeping Jira and Confluence in sync. This guide walks you through configuring AutoPage rules within Jira.

The rule defines:

  • Which template is used for which Jira issue(s)
  • Under which parent page the generated Confluence pages are created

JiraRuleOne

Click “Create new rule” in the upper right corner.
You can always see on the label in the upper right if you are creating or editing a rule.


ParameterDescription
Rule NameName of the rule.
Rule StatusIf active, the rule is evaluated. If inactive, it’s not applied.
TriggerDefines when the rule runs: Issue Events, Jira Post Function, or Sprint Events.
Issue Event TypesChoose which issue events should trigger the rule. Select All Events to listen to all. (Visible only for Issue Events trigger)
Sprint Event TypesChoose which sprint events should trigger the rule. (Visible only for Sprint Events trigger)
BoardSelect a Jira Board for which the sprint rule should apply. (Visible only for Sprint Events trigger)
Use explicit executing userEnables specifying a fixed user to create/update pages. That user must have permission in Confluence.
Executing userJira user on whose behalf rules run. Must be an admin in both Jira and Confluence. (Visible when using explicit user or Sprint Events)
JQL FilterJQL to filter which issues apply. Only evaluated when using Issue Events trigger.
Confluence Space KeySpace in which pages are created.
Confluence Template PageTemplate page used for the content.
Confluence Page TitleTitle of the generated pages. Supports placeholders like $#Key and $#{sprint_id} for uniqueness.
Confluence Page LabelsOptional. Can also use placeholders for dynamic labels.
Parent PageDefines how to choose the parent page. Options: fixed page, another rule’s page, or a custom field.
Create Remote Issue LinkCreates a link to the generated page in the Jira issue’s “Issue Links” panel.
Issue Link NameName of the link type in the Jira panel (e.g., “Quest Description”).

JiraRuletwo

In the rule overview, you can delete the rule by clicking on the Delete icon in the upper right.

JiraRulethree

There are several strategies to determine the parent page in Confluence:

  • Fixed Page: Choose a specific Confluence page.
  • From another Rule: Use the page generated by a different rule.
  • Parent Issue Page: Use the page generated for a parent issue (e.g., Epic or main task).
  • From Custom Field: Dynamically choose the parent page using a custom Confluence Page Search field.

Allows you to rebuild all previously generated pages using the latest template.
Useful when:

  • Updating the template
  • Reapplying changes to all pages

⚠️ Manual changes will be overwritten, but page history remains intact.

JiraRulefour

Trigger AutoPage from a Jira Post Function (e.g., “Reopen Issue” transition):

  1. Set the rule’s trigger to Post Function
JiraRulefive
  1. Add an “AutoPage Post Function” to your Jira Workflow
JiraRulesix
  1. Select the rule you want to execute
JiraRuleseven

You can edit, delete, or reorder the post function like any other.

JiraRuleeight

Triggers rules based on Sprint Events:

  • Choose a board
  • Choose an executing user (admin in both Jira and Confluence)
  • All other parameters behave the same as other triggers

New placeholders for sprints are available in this mode.

JiraRulenine

📁 Parent Page from Custom Field (v2.6.0)

Section titled “📁 Parent Page from Custom Field (v2.6.0)”

Allows dynamic parent page selection using a Confluence Page Search field:

  • Add a custom field of type: Confluence Page Search (AutoPage)
  • Configure it to appear on issue create/edit screens
  • Choose this field in your rule’s parent strategy
  • Supports also a plain text field with a page ID
JiraRuleten

When creating an issue first choose the Confluence space and then your parent page.

JiraRuleeleven

After issue creation:

  • The parent page appears in the Jira detail view
  • Changing it updates the Confluence hierarchy automatically
JiraRuletwelf

Set a specific user to always execute the rule (vs. the ticket updater):

  • Recommended: create a dedicated AutoPage User
  • Ensures proper permissions for consistent page creation
JiraRulethirteen

Trigger permission changes via a Post Function:

Options:

  • Editing restricted: Only specified users/groups can edit
  • Viewing and editing restricted: Only specified users/groups can view or edit

🔒 The executing user is always exempt from restrictions to avoid self-lockout.