Examples

AutoPage - Examples

This section provides examples of common AutoPage configurations to help you set up various automation scenarios.

Generate More Than One Page From One Issue

For a quest ticket, we want to create a subpage with equipment and a subpage for side quests. For this, we create 2 more template pages. The page with the side quests is a simple blank page.

We created a new rule for the base equipment. As Parent Page, we are using the generated Page from the Quest Pages Rule. The same procedure is used for the side quests page.

As a result, the two generated pages AP-1 - Equipment and AP-1 - Side Quests are added under the page Quest AP-1 - Save the princess. AutoPage ensures that first the parent page, in this case Quest AP-1 - Save the princess is generated and then the subordinated pages are generated.

Generate Pages for Subtasks

We want to create side quests as subtasks. For each subtask we want to create a page under the generated “Side Quests” page.

Note that the JQL restricts this rule to subtasks (project = AP AND issuetype in subTaskIssue Types ()).
For the other rules, the JQL must be edited so that it does not apply to the subtasks (project = AP AND issuetype in standardIssue Types ()).

As a result, one page is created for each subtask under the page “Side Quests”.

Generate Pages via Post Function

Let’s say we want to create or update Quest Pages only after a specific workflow-transition, e.g., “Start Progress”. Therefore you can use the Post Function Trigger to integrate the AutoPage rule with plain JIRA Post Functions.

The only thing you’ll have to change is the Trigger Parameter. When you are in the Post Function Selection Dialog, choose AutoPage Post Function from the list. On The Add Parameters To Function Dialog, choose our created rule “Quest Pages” and submit the selection with a click on Add.

If everything went fine, the selected Post Function will be displayed on the Transition screen under the tab Post Functions. Now you’ll only have to publish your workflow which enables our changes.

If you want to delete or disable your Post Function rule, AutoPage will notice and display a message in the Post

Generate more than one page from one issue

We’ve used the following rule to create a quest page for a quest ticket.

For the quest we want to create a subpage with equipment and a subpage for side quests. For this we create 2 more template pages. The page with the side quests is a simple blank page.

We created a new rule for the base equipment. As Parent Page we are using the generated Page from the Quest Pages Rule. The same procedure is used for the side quests page.

Generate pages for subtasks

We want to create side quests as subtasks. For each subtask we want to create a page under the generated “Side Quests” page.

We create a new template and a new rule. The “Parent Page Rule” is the Side Quests Rule. Additionally, the option “Use parent page from parent Issue” is now active and ensures that we use the generated page from the parent issue of the subtask. Note that the JQL restricts this rule to subtasks (project = AP AND issuetype in subTaskIssueTypes ()). For the other rules, the JQL must be edited so that it does not apply to the subtasks (project = AP AND issuetype in standardIssueTypes ()).

As a result, one page is created for each subtask under the page “Side Quests”.

Generate pages via Post Function

Let’s say we want to create or update Quest Pages only after a specific workflow-transition, eg. “Start Progress”. Therefor you can use the Post Function Trigger to integrate the AutoPage rule with plain JIRA Post Functions. The only thing you’ll have to change is the Trigger Parameter to match the picture on the right.

To add a plain JIRA Post Function see this link: Advanced workflow configuration

When you are in the Post Function Selection Dialog, choose AutoPage Post Function from the list.

On The Add Parameters To Function Dialog, choose our created rule “Quest Pages” and submit the selection with a click on Add.

If everything went fine, the selected Post Function will be displayed on the Transition screen under the tab Post Functions. Now you’ll only have to publish your workflow which enables our changes.

If you want to delete or disable your Post Function rule, AutoPage will notice and display a message in the Post Function list. You can then select a new rule or delete the Post Function entirely.

Page properties report to list generated pages

For the Side Quests page, an overview of the generated pages in Confluence will be created. This can be particularly useful if you have many generated pages and want to see an overview of these pages. Using the Table Filter app for Confluence, you can also use filters (such as status) to identify the generated pages. We’ll update our Side Quest template to include the page properties macro. On a new page we will generate the Page properties report. For the individual Side Quest pages, we have added the label “sidequest” to each page using the Side Quest rule. The label can now be used in the page properties report.

Create a hierarchy with Epic-Story-SubTask relationship

Epic rule

First create a rule for your epics:

Story under epic rule

Then you should create a rule for all stories that will be created under an epic:

SubTask rule

The last thing that needs to be done is a rule for the SubTasks that are going to be under the story: