Add comment | Decadis App Help Center

The Add comment post function automatically creates a comment in the current, parent or any issue(s) returned by a parser expression. The comment text can be composed of free text in combination with field codes or functions provided by the selected parsing mode.

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

⚒️ Configuration

Target issue

Select the issue the comment will be added to. The following options are available:

Current issue
Parent issue
Selected issue
Parser expression

When the option parser expression is selected, an expression parser input field is displayed and the input has to be an issue key or an issue list. The comment will be added to every issue in the given issue list.

Comment text

Enter the comment's text that will be created. You can enrich the styling of your comment by using the avaible markdowns.

If you would like to mention a user, you can use a markdown like the following

Bash

Hi [~accountid:%{issue.reporter}], 
this issue needs your immediate attention.

Thanks, 
%{system.currentUser.displayName}

The length of the comment's text is restricted to 5000 characters.

Comment author

Select the user that will be used to execute the post function. By default, it is set to the current user that executes the transition.

The following options are available:

Option	Description
Selected user	Select a specific Jira user.
User in field	Select the field containing the user that will be used to execute the post function.

The configured user must have all necessary permissions to create the comment in the target issue.

Comment visibility

Select the comment visibility.

For Jira:

Unrestricted (all users)
Restricted to Project Role
Restricted to Group

For Jira Service Management:

Reply to customer
Add internal note

If the comment should be restricted, the configured comment author must be a member of the configured role or group.

Conditional execution

You can optionally specify a logical expression or a Jira expression depending on the chosen Parsing mode to define the circumstances (or conditions) under which the post function should be executed.

The result of the logical expression must return a boolean value of either:

true → the post function will be executed
false → the post function will not be executed

Using the conditional operator, even complex or multi-layered conditions can be constructed.

Make sure to learn more about defining logical expressions and browse through the various examples here: Logical mode

📚 Use cases and examples

Use case	Workflow function	Use case description
Add a comment with links to attachments that were just added	Add comment	A comment will be added to the current issue with links to the attachments included recently.
Add comment when rejecting an issue	Add comment	When an issue is rejected, a comment will be added to the current issue mentioning the reporter.
Add formatted comments automatically	Add comment	Add a formatted comment to the current issue. It would be convenient in case that you need to create a table or highlight some important points in the comment.
Alert the assignee of important issues	Add comment	Add a comment to an issue mentioning the assignee. The comment will only be added, if the issue priority is set to "High" or "Highest" to ensure that the assignee will only be alerted for the important issue
Alert the reporter	Add comment	Add a simple comment to an issue mentioning the reporter. This use case might come in handy if you don't want to use extra events in your notification schemes to notify specific users - like the reporter.
Push status updates to the linked Epic	Add comment	Add a comment to the linked Epic including the summary and status of the current issue. This is helpful when you don't want to keep track of individual Stories and only receive notifications of the linked Epic (e.g. as a watcher or reporter).
Push status updates to the parent	Add comment	Add a comment to the parent issue including the summary and status of the current issue. This is helpful when you don't want to keep track of individual sub-tasks and only receive notifications of the parent issue (e.g. as a watcher or reporter).