Versions Compared

Key

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

A workflow post-function that creates a comment on the current issue or issues related to the current issue. The text of the comment to be created can be any simple text or a text with Nunjucks annotations.

When you add this post-function to a transition and trigger the transition, the add-on picks the value entered in the Comment field and adds it as a comment on the target issue(s). The Comment to be created can be any simple text, or you can also use Nunjucks annotations to insert other issue data into the Comment text, including issue, transition and current user information To find out more about using variables, see Using Nunjucks Templates.

To add 'Comment issue(s)' post function to a transition: 

  1. Click Edit for the workflow that has the transition you wish to add the post-function on.

  2. In the Workflow Designer, select the transition.

  3. Click on Post Functions in Functions in the properties panel.

  4. Click on Add   post function.

  5. Select Comment issue issue(s) from the list of post -functionsfunction.

  6. Click on  Add to add the navigate to the Comment issue(s) post-function on the transition.

  7. Select the “Target issue” (see below)

  8. Input a comment in the Comment field.
    To input issue or transition or currentUser information in the Comment field see, Using Nunjucks Templatesscreen where you can add configuration details to the post function. See below for more information.

  9. Click on Add to add the post - function to the transition.

  10. After adding, move the post-function to the appropriate position according to Placing post-functions in a transition document.

Info

You are viewing the documentation for Jira Cloud.

On This Page

Table of Contents
minLevel1
maxLevel2
outlinefalse
typelist
printablefalse
Image Removed

  1.  

Info

JMWE shows an error message on the issue view if any error occurs during the execution of the post-function. This message is only displayed if the current user is a Jira administrator. 

When you add this post-function to a transition and trigger the transition, the add-on picks the value entered in the Comment field and adds it as a comment on the target issue(s). The Comment to be created can be any simple text, e.g. This is a comment. You can also use Nunjucks annotations to insert issue, transition and current user information into the comment text, using the 'issue', 'transition' and 'currentUser' variables, respectively. To find out more about the variables, see How to insert information using Nunjucks annotations.

Issue(s) to operate on

Select the issues to operate on. They can be:

  • Target issues

    • Current issue: Select this option to

add a comment on
    • set the assignee of the current issue. This is the default option.

    • Sub-tasks of the current issue: Select this option to

add a comment on each
    • set the assignee of sub-

task
    • tasks of the current issue

    • Parent issue of the current sub-task: Select this option to

add a comment on
    • set the assignee of the parent of the current issue

    • Issues that belong to the current issue (Epic): Select this option to

add a comment on the
    • set the assignee of issues that

belong
    • belongs to the current Epic

    • Epic of the current issue: Select this option to

add a comment on the parent
    • set the assignee of the Epic of the current issue

    • Child issues of the current issue in the Portfolio hierarchy: Select this option to

add a comment on the
    • set the assignee of child issues of the current issue in the Portfolio hierarchy

    • Parent issue of the current issue in the Portfolio hierarchy: Select this option to

add a comment on
    • set the assignee of the parent issue of the current issue in the Portfolio hierarchy

    • Issues linked to the current issue through any link type: Select this option to

add a comment on all issues linked to the current issue
    • set the assignee of the current issues' linked issues

    • Issues linked to the current issue through the following link type: Select this option to

add a comment on the
    • set the assignee of issues linked to the current issue through a specific link type. Select the specific link type under “Issue link”

    • Issues returned by the following Nunjucks template: Select this option to

add a comment on
    • set the assignee of the issues returned by the result of a Nunjucks template. Input a Nunjucks template which is a comma-separated list of valid issue keys. For example:

      • "TEST-1"

      • "TEST-1","TEST-2"

      • {{ issue.fields.parent.key }}

      • {{ issue.fields.subtasks | join(",", "key") }}

    • Issues returned by a JQL search: Select this option to

add a comment on
    • set the assignee of the issues returned by a JQL search. Input a JQL search expression. For example:

      • project = TEST returns issues of the project with the key TEST

      • project = {{ issue.fields.project.key }} and assignee = {{currentUser._accountId}} returns issues of a project that belong to the project with key TEST and the assignee is the current user

      • Code Block
        {% if issue.fields.assignee %}
            assignee = {{issue.fields.assignee._accountId}}
        {% else %}
            issuekey=INVALID-1
        {% endif %}

        Note that the {% if %} block is necessary to avoid an invalid JQL query when the issue is unassigned. In that case, the template will return a valid JQL query that returns no issue (issuekey=INVALID-1).

  • Issue Link - Only available when Target issues, above, is set to Issues linked to the current issue through the following link type. Select the required link type between the current issue and the issue to be updated.

  • Nunjucks template - Only available when Target issues, above, is set to Issues returned by the following Nunjucks template. Enter a Groovy script that returns the ID values for the issue or issues to be updated. See Using Nunjucks Templates for more information on Nunjucks.

  • JQL expression - Only available when Target issues, above, is set to Issues returned by the following JQL search. Enter a JQL expression that returns the ID values for the issue or issues to be updated. See Using Jira Expressions for more information on JQL.

Comment

Enter the comment to be added to the target issues in the Comment script editor field.

Advanced options

Expand this section to see advanced configurations including which user will run the post function, conditional execution, and delayed execution.

Comment visibility

You can set the visibility of the comment using these options. For no restrictions, leave these fields blank.

  • Restrict to Group

:
  • -Restricts the visibility of the comment to a specified group. When you select a valid group name in

the Restrict to Group field
  • this field, the comment will be visible only to the members of

the specified
  • that group.

For no restriction, leave the field blank.
  • Restrict to Project Role

:
  • -Restricts the visibility of the comment to a selected project role. When you select a project role

from the drop-down Restrict to Project Role field
  • , the comment will be visible only to the members of

the selected project
  • that role.

For no restriction, leave the field blank.
  • Restrict to Internal (Jira Service Desk only)

:
  • -Restricts the visibility of the comment to

the To execute this post-function based on the result of a Nunjucks template see Conditional execution.
  • Service Desk Agents and Collaborators only.

Run As

  • Run as current user: The current user will be the author of the comment created on the issue by the post-function. 

  • Run as add-on user: The add-on user will be the author of the comment created on the issue by the post-function. 

  • Run as this user: Any user selected in this field will be the author of the comment created on the issue by the post-function. 

Conditional execution

  • Save the post-function

  • Publish the workflow

  • See here for more use cases
    Include Page
    [Includes] Post-function - Run As
    [Includes] Post-function - Run As

    Conditional execution

    Include Page
    [Includes] Post-function - Conditional Execution
    [Includes] Post-function - Conditional Execution

    Delayed execution

    Include Page
    [Includes] Delayed Execution
    [Includes] Delayed Execution

    Use case

    A typical use of this workflow post-function is to comment on an issue during a transition. Consider a use where on resolving/closing a ticket you want to comment on the issue a summary of the worklog. To configure it:

  • Add the Comment issue post-function to the Resolve transition of the issue's workflow.

  • Write the following content in the Comment section.

    Code Block
    {% set worklogs = issue.fields.worklog.worklogs %}
    {% set count = 1%}
    {% for worklog in worklogs %}
    Worklog {{count}}:
    Started : {{ worklog.started }}
    Time Spent : {{ worklog.timeSpent }}
    Work Description : {{ worklog.comment }}
    
    {% set count = count + 1 %}
    {% else %}
    No work logged for this issue
    {% endfor %}

    You are viewing the documentation for Jira Cloud.

    On This Page

    Table of Contents
    minLevel1
    maxLevel3
    outlinefalse
    styledefault
    typelist
    printablefalse

    Comment issues post function configuration screenImage Added