Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Selecting the template page
    You can choose any page in your Confluence to be a template for this post function. See creating a template page with dynamic parameters.
    There is a Confluence Search input in which you can start typing the title of Confluence Page. 


    We're not currently supporting Confluence Templates, please select any page as a template.

    The selected page will automatically fill Page ID. If you know the page ID of the template page, you can skip above step and fill the ID instead.

  2. Selecting the folder where generated pages will be created
    Similar to the first step, choose the folder (Confluence Page) where you want your automatically created Confluence pages will be created. 
  3. Page Content
    Page title and content is 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 experienced user, and you want to follow the standards. Click on Load default body to modify 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 Confluence pageuserDisplayName =


    assignee = $issue.assignee or {{





    assignee =

    reporter = {{issue.reporter}}
    date = $issue.


    formattedDate = $DateTimeFormatter.ofPattern("yyyy-MM-dd HH:mm").format($issue.created)
    productName = $issue.getCustomFieldValue($customFieldManager.getCustomFieldObject('customfield_11100'))
    price = $issue.getCustomFieldValue($customFieldManager.getCustomFieldObject('customfield_11102'))
    displayName = $user.displayName
    userDisplayName = $ComponentAccessor.getUserManager().getUserByName("someUser").getDisplayName() // you can also use ComponentAccessor
    story point = $issue.getCustomFieldValue($customFieldManager.getCustomFieldObject('customfield_11100'))
    environment = Production
    comment = $comment // this is the comment that is passed through the transition


    If you want to leave empty if no value specified, add ! after $ sign. e.g.:

    story point = $!issue.getCustomFieldValue($customFieldManager.getCustomFieldObject('customfield_11100'))