# Configuring manual emails

Configure the default recipients, templates and various other settings of manual emails the following way:

1. Go the **Outgoing Mails** configuration tab and select **Manual Email Configurations** under **GENERAL CONFIGURATION**.
2. Add a new configuration by clicking on the **Add** button.
3. Edit existing ones by clicking on the three dots and choosing **Edit**.

<figure><img src="/files/LdGu1qJJ5FUlQkryXDBa" alt=""><figcaption><p>Editing existing Manual Email Configuration</p></figcaption></figure>

{% hint style="info" %}
Note: It is possible to add multiple manual email configurations. Consider these aspects in each case:

* **Scope -&#x20;*****WHEN***&#x20;
* **Default Recipients -&#x20;*****WHO***
* **Content Settings -&#x20;*****WHAT***
* **Comment Settings**
  {% endhint %}

## **Setting up** Scope - *WHEN* <a href="#manualemailconfiguration-scope" id="manualemailconfiguration-scope"></a>

The scope determines which issues this setting is applicable to. If there are multiple manual email configurations, Email This Issue evaluates all of them and determines the one with the best matching scope for each specific issue.

The scope can be composed of:

* 0 or more projects&#x20;
* 0 or more issue types
* An optional JQL query

The following example matches issues with the highest priority with the **Issue Type** "Sub-task" in the "ITSM" **Project**.

<figure><img src="/files/OEGEcDWH6gZw0nSwgSjk" alt=""><figcaption><p>Scope - WHEN</p></figcaption></figure>

To enter a JQL which involves a user name (such as defining the assignee of an issue), follow these steps:

1. Under the **JQL Filter** field, click **Edit**.
2. Enter the JQL.
3. When it comes to entering a user name, do the following:
   1. &#x20;Click **Insert user**.&#x20;
   2. Search for the user name, then click on **Insert** to insert a string.
4. Click **Save** to use the JQL or **Cancel** to delete it.

{% hint style="info" %}

#### Scope evaluation

Scope evaluation is an important part of Email This Issue. For more information, see [Scope Evaluation](/email-this-issue/outgoing-emails/email-this-issue-for-jira-cloud-scope-evaluation.md).
{% endhint %}

## **Setting up** Default Recipients *- WHO* <a href="#manualemailconfiguration-defaultrecipients" id="manualemailconfiguration-defaultrecipients"></a>

Here, you can define the recipient settings that are automatically selected in the [The Email Button and the Email Screen](/email-this-issue/outgoing-emails/manual-emails/email-this-issue-for-jira-cloud-the-email-button-and-the-email-screen.md). This makes email composition a lot easier and less prone to errors.

Predefined recipients help users not to forget to include important stakeholders who might be interested in receiving the emails.

Emails can have **To**, **Cc** and **Bcc** recipients. For all of these recipient types you can enter or select:

* Users from Jira
* Email addresses
* Users related to the issue or project, such as:
  * Assignee
  * Reporter
  * Watchers
  * Project Lead
  * Current User
* Project Roles
* User Groups
* Custom Fields, that hold email addresses or users or groups

The following example defines the **Recipient(s) To** as the "Reporter" and **Recipient(s) Cc** as the "Request participants".

<figure><img src="/files/BjIa4ihXAcIHaT8dwfBR" alt=""><figcaption><p>Default Recipients - WHO</p></figcaption></figure>

{% hint style="info" %}
Note: Available user groups, project roles and custom fields may be limited under [Recipient Restrictions](/email-this-issue/administration/email-this-issue-for-jira-cloud-recipient-restrictions.md). This is useful if you want to avoid users accidentally selecting the "jira-users" group as a recipient, and send emails to all users.
{% endhint %}

## **Setting up** Content Settings - *WHAT* <a href="#manualemailconfiguration-contentsettings" id="manualemailconfiguration-contentsettings"></a>

These settings define the templates and default responses available in the [The Email Button and the Email Screen](/email-this-issue/outgoing-emails/manual-emails/email-this-issue-for-jira-cloud-the-email-button-and-the-email-screen.md).

Fields available under Content Settings:

| Field               | Value                                                                                                                                                           | Definition                                                                                                                                                                                                                                                                                                                                                                       |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Template            | [Customizable Email Templates](/email-this-issue/outgoing-emails/email-this-issue-for-jira-cloud-customizable-email-templates.md)                               | <p>The template selected here serves as the default template for the manual email configuration.</p><p>This is a mandatory field.</p>                                                                                                                                                                                                                                            |
| Template Categories | Category Names of [Customizable Email Templates](/email-this-issue/outgoing-emails/email-this-issue-for-jira-cloud-customizable-email-templates.md)             | The templates belonging to categories selected here will be available on the Email Screen.                                                                                                                                                                                                                                                                                       |
| Canned Responses    | Category Names of [Default Messages (Canned Responses)](/email-this-issue/outgoing-emails/email-this-issue-for-jira-cloud-default-messages-canned-responses.md) | <p>The <a href="/pages/-Mf8I45fTzHq8rpzpTok">Default Messages (Canned Responses)</a> of the categories selected here will be available on the email screen and can be added to the email body.</p><p>Canned Responses make it extremely easy and convenient to add complex, standardized texts to emails. With Canned Responses, users do not have to type in long messages.</p> |
| Email Format        | HTML or Text                                                                                                                                                    | <p>The format of the emails sent in the scope of the specific manual email configuration.</p><p>If set to HTML, the HTML parts of the template will be used. If set to Text, the text parts of the template will be used.</p>                                                                                                                                                    |

Example:

<figure><img src="/files/Lb94lyAJTuv2yVwpdTki" alt=""><figcaption><p>Content Settings - WHAT</p></figcaption></figure>

## **Setting up** Comment Settings <a href="#manualemailconfiguration-additionalsettings" id="manualemailconfiguration-additionalsettings"></a>

Email This Issue may add a comment to the issue when it is sent in email. Additional Settings specify the following:

| Setting                   | Value                                                       | Definition                                                                                                                              |
| ------------------------- | ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Add Comment to Issue      | On/Off                                                      | If switched on, Email This Issue adds a comment to the issue when the email is sent.                                                    |
| Comment Author            | The user who sent the email/"Email This Issue" (addon-user) | If The user who sent the email is selected, comments are added as the current user. Otherwise the author appears as "Email This Issue". |
| Email Details in Comments | On/Off                                                      | If switched on, Email This Issue adds email details to the comments, such as recipients, email subject and attachments.                 |
| Comment Visibility        | <p>All Users</p><p>or Project Roles</p><p>or Groups</p>     | This field specifies if the comment is to be visible to all users or to be limited to a project role or a user group.                   |

Example:

<figure><img src="/files/kSoQSFMiCohH2AmdMao3" alt=""><figcaption><p>Comment Settings</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.meta-inf.hu/email-this-issue/outgoing-emails/manual-emails/email-this-issue-for-jira-cloud-manual-email-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
