...
At Attachment handling you can configure when you want to add the attachments to the issue. There are 4 6 options you can select from:
- Never add
- Skip if attachment name matches any of the following regexes
- Skip if attachment with the same name exists
- Skip if attachment with the same name and size exists
- Skip if attachment with the same hash exists
- Always add
| Info |
|---|
Issue creation is done as well in case the email arrives with an empty body. Description will be left empty, or will be filled with a placeholder, if the field is required on the issue. |
Update issue
This action can be used to update (set field values) an existing issue. Currently it has no parameters, by default it does nothing, add Set field value actions under this action to update multiple fields in a single step.
...
And currently supported sources are:
- Participants' email addresses: You can select which participants' email adresses you want to use as a value. Participants can be any of the following: To, From, Cc, Bcc
- Participants' names: You can select which participant participants' names you want to use as a value. If the participants don't have a name, their email addresses will be used. Participants can be either any of the following: To, From, Cc, Bcc
- Extract from email body/subject: Source is either the subject or the body of the email. You can define a regex and refer to the group which contains the value to set. Group 0 means the whole text.
| Note |
|---|
If you are using the set field value action with the create issue action and you are creating a request, you have to add the field to the Request Type and make it visible on the portal. Remember, you cannot add an Assignee to the portal, and that's why it cannot be set during request creation. As a work-around, you can create the request, set the fields and in a the next action, update the 'Assignee' field. |
...
| Note |
|---|
If you want to add the sender as a Request participant to the request, use the Add sender to requet request participants action. |
Add comment
Split regexpregex can be used to keep only the first part of the body before a pattern that is specified in the regexpregex. Note that multiple regular expressions can be defined (each on a new line) and they must begin and end with a / sign, like: /Re:/
| Note | ||
|---|---|---|
| ||
Please note that during processing before splitting the mail body by regexpregex, the whole body is converted to Jira wiki format and regexp the regex is applied on the converted value. for For more details please check 72116295 |
...
- Service Management allows you to make the comment private
- Project Roles allows you to restrict comment visibility on Project Roles
- Groups allows Groups allow you to restrict comment visibility on Groups
If you don't want to put any restriction on the comment, just set it to 'All users'.
Add The add comment action has the same Attachment handling strategies as the 72116295 action has.
| Info |
|---|
Comments now can be added to sub-tasks in Service Management projects. The visibility of the comments can be internal, but attachments cannot. |
Send auto-reply emails
Use this action to send auto-replies. The same templates can be used that are listed under Outgoing Mails/Templates
...
If there are multiple transitions to this destination status, then the preferred one can be choosen chosen in the Use transition field by setting the id or the name of the transition. When the name is specified, then a regexp can be used as well. Note that only one regexp is allowed.
By the default, the first found transition is used to move the issue to the required destination status
...
You have to provide a Service Management project to which you want to assign the customer.
...
During processing before splitting the mail body by regexp, the whole body is converted to Jira wiki format and regexp is applied on the converted value.
This means that in the case of html HTML emails, regexps regexes must be written for wiki format.
...