要約

Emails sent to your Jira Service Management project(s) are not creating issues, or they are not arriving at JSM's email channels.

Test your email channel connection

Errors with your email channel connection can occur for a variety of reasons. To check if your Service Management can receive email requests, test the connection between your Jira Service Management and your email account. To check your email channel connection:

You must be a Jira admin to check the connection. The Test function is only available for custom email channels, not Atlassian email channels. 

1. Choose Settings  > Products.
2. Under Jira Service Management, select Email Requests.
3. Select Actions next to the desired channel > Test connection.

Adjust the global mail settings

You can temporarily adjust the Global email settings to troubleshoot your email channel.

To change the global mail settings:

You must be a Jira admin to check the connection.

1. Choose Settings  > System.
2. Navigate to the Global Mail Settings option.

1. Email address in use

メッセージ

The email address you entered is currently used by another project's email channel.

ソリューション

Make sure each of your Service Management projects has a unique email account. An email account can't connect with multiple Service Management projects.

You can also receive this message if you're trying to use multiple email aliases that point to the same email account for multiple Service Management project email channels.

2. Requests are not created or notifications received

説明

Customers are emailing requests that are not arriving in your queues. They also are not receiving notifications.

ソリューション

To troubleshoot why requests are not created or notifications received:

1. Check the email connection.

2. Verify that the customer has permission to email your Service Management project.

3. メール チャンネルのデフォルト リクエスト タイプで [概要] フィールドと [説明] フィールドが表示されていることを確認します。

4. Verify if another Jira instance email channel/mail handler is intercepting mail items intended for the target instance.
   • With debug logging enabled for incoming mail you should find a "found x messages for processing" each time the mail puller is run.
   • If you do not see a matching quantity of mail items pulled for processing as what was sent to the mailbox, there may be something else pulling the email before the target instance is able to.

5. Verify that the Email puller is on in Global mail settings.

   • If the associated email inbox is in Office 365, it might be because an attachment on the request is larger than 2MB.

     • This is a known issue with Office 365 - to resolve it, try resizing the attachment.

   • If the associated email is AOL, the AOL mail server might reject the mail.

     • This is because the Atlassian Cloud mail server is not a fully-qualified domain name (FQDN).

     • We recommend that you don't use AOL email addresses with your Service Management project.

6. Verify if the email already been read before the email processor tried to process the email.
7. If yes, set the email back to "Unread" mode and monitor the processing log for the email to process successfully.

3. Requests not created due to too many required fields 

メッセージ

Configured request type has too many visible required fields.

ソリューション 

This issue occurs when fields other than the Summary (Subject) and Description (Body) are marked as required for the request type used by the email channel. To resolve this issue:

1. Within your Service Management project, navigate to Project Settings  > Request Management > Request types.
2. Identify and select the request type used by the Email channels.
3. Select Request form.
4. Confirm that only the Subject or Body fields are marked as Required.
5. If other fields are marked as Required, adjust the value within the Required column to No and select Update to save your changes.

4. No suitable request type for the email channel

メッセージ

No suitable request type for the email channel. You will select the default request type assigned to requests created from the email channel during the setup. However, no existing request types are suitable for email requests. A suitable request type must have both the Summary and Description fields as visible fields and all the other visible fields, if any, must be optional. If you want to enable the email channel, add a new request type that meets the criteria or modify an existing one on the Request types page.

ソリューション

To troubleshoot why there are no suitable request types for the email channel:

1. In your Service Management project, select Project Settings > Request Management > Request types.

2. 新しいリクエスト タイプを追加するか、既存のリクエスト タイプを選択します。

3. Select Edit fields.

4. Make sure both the Summary and Description fields are added and marked as Visible. 

5. Add an Attachment field and mark it as Not Required.

6. Select Save, then head back to Project settings > Channels & Self-Service > Email requests.

5. Archived messages are creating requests

Description
When Jira Service Management checks your email accounts for new messages, it polls the inbox folder. Gmail uses labels to classify messages into categories and only has the following folders:

• 受信トレイ

• 送信済みメール

• ビン(ゴミ箱)

つまり、アーカイブ済みメッセージはまだ受信トレイ フォルダ内にあるとみなされます。POP3 を使用している場合、Jira Service Management はラベルによってアーカイブ済みメッセージを識別できないため、リクエストとして処理します。

ソリューション

Use IMAP instead, or reconnect with OAuth by clicking on the Microsoft logo.

6. Set up a Gmail account

メッセージ:

Unfortunately Jira couldn't connect to the mail server. Here is what the mail server said: "[ALERT] Please log in via your web browser:http://support.google.com/mail/accounts/bin/answer.py?answer=78754(Failure)"

解決状況：

Create an application-specific password for Jira Service Management in your Gmail account settings.

7. Account locks for security - Microsoft Outlook

メッセージ:

Unfortunately, Jira Service Management couldn't connect to the mail server. Here is what the mail server said: "STAT command failed: Exceeded the login limit for a 15 minute period. Reduce the frequency of requests to the POP3 server.

解決状況：

Jira Service Management checks email accounts every minute. Microsoft Outlook might suspect inappropriate usage of this account and lock it for security reasons. To resolve this, use IMAP instead, or reconnect with OAuth by clicking on the Microsoft logo.