Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

On this page


Introduction

The Add comment post function automatically creates a comment in the current, parent or any issue returned by a parser expression. The comment text can be composed of free text in combination with various fields using their field codes.

The comment author can be selected among various user fields and the visibility can be restricted by project role or by user group.


Remark

In this documentation and the post function configuration you will notice the symbol ( * ) next to some parameters, it means that this field is mandatory and shall not be left empty. Fields without the symbol are optional.

Basic configuration*

Below you will find a detailed description of each parameter of the basic configuration of the function.

Comment text*

Define the content of the comment by choosing one of the following options:

  • Add comment manually /parser expression)
  • copy field value from current issue

Issue type*

The issue type of issue(s) to be created. The following options are available:

  • Selected issue type

  • Parser expression (standard issue type)

    ((info) expects an issue type ID or reference like %{issue.issueType.id} )

  • Parser expression (sub-task issue type)

In case a sub-task is chosen, the respective parent has to selected and the following options are available:

  • Current issue
  • Parent issue
  • Selected issue
  • Parser expression ((info) the input has to be an issue key)

The parent issue is only shown when a sub-task is selected as issue type.

Project (only for standard-issue types)*

The project that the issue will be created in will come with the following options:

  • Current project
  • Selected project
  • Parser expression ((info) the input has to be a project ID or a reference like %{issue.project.id})
Please note that the project selection does not show up when the issue type is a sub-task.

Fields*

Summary*

Enter a text to give a summary to your issue (like a title for the issue), and you can also use field codes.

Description

Enter a text to describe your issue.

Additional fields

Set additional field values, in the popup after clicking the Add button you can select to set the value in two ways:

  • Copy field from the current issue (the value from the selected field will be copied over to the new issue)
  • Set field value manually (expression parser)

You have the option to link the issue that you are currently creating to an existing issue, and you have the following options:

  • is blocked by (Blocks) -inward
  • blocks (Blocks) -outward
  • is cloned by (Cloners) -inward
  • clones (Cloners) -outward
  • is duplicated by (Duplicate) -inward
  • duplicates (Duplicates) -outward
  • relates to (Relates) -inward
  • relates to (Relates) -inward

Conditional execution

Enter a condition (Boolean condition) using the JWT expression parser - full feature list syntax.

You can even logically link and gather conditions in expressions as you like in order to map more complex conditions.

The post function will only be executed if the condition is met (returns true .).


Use cases and examples using this post function

Use case
No content found.


If you still have questions, please refer to our support team.