Excerpt | ||
---|---|---|
| ||
Post function to automatically create Confluence page within JIRA workflow |
Create Confluence Page Post functions automatically creates Confluence pages via JIRA workflow.
To add Create Confluence Page using a template page post function, go Easy Integration comes with a handy post function in order to create Confluence pages via JIRA workflow transition. Issue's field / custom field values can be used to generate Confluence pages from templates.
Here are the steps:
- Go to the desired transition of your workflow, switch to Post functions tab and click on Add post function link.
...
- Locate Create Confluence Page using a template page
...
- post function and click Add button.
0 - Type of Confluence Connection
You can define This initial step is to select the Confluence connection type. You have There are two options;:
- Credential: Choose Credential if you want to use Confluence Integration Credential which defined here. If you don't define it, you won't see this optionconnection which is defined via Easy Integration Confluence setting. If there is no defined credential, this option won't be seen.
- Application Link: Use Application Link when a connection to Confluence. You can select any application link which type is Confluence in your JIRA. If you don't have any application link, you won't see this optionIf you want to use Jira application link, choose this option. If there are multiple application links, you can choose appropriate one, if there is no application link in your Jira, this option won't be seen.
Condition
In this part, you can add a condition for the confluence page. By default, it has only return true statement which means that the Confluence page will be created. However, you can type your own script in order to programmatically add a condition to create a Confluence page or not.
...
Page title and content are defined in this section.
Page Title: As you know, Confluence does not permit the same page title within the same space. So, adding a unique key to the page (like JIRA issue key) would be wise
Request body: Leave blank if you are not an experienced user, and you want to follow the standards. Click on the Load default body to modify the link if you want to see and change the request JSON body. Otherwise, leave blank.
Parameters: Add static or dynamic parameters here. Some sample parameters are shown below. These parameters can be used within double curly-braces in a Confluence page
Some code example below;
Panel |
---|
assignee = $issue.assignee or {{issue.assignee}} reporter = {{issue.reporter}} |
...
Info |
---|
If you want to leave empty if no value specified, add ! after $ sign. e.g.: story point = $!issue.getCustomFieldValue($customFieldManager.getCustomFieldObject('customfield_11100')) |
Click the Add button, and that's it. Please do not forget to publish the workflow.
...