Issue not creating from Mail Handler Test mode

[Horace Su]

Hi Team,

I'm having a problem with the mail handler, I will start with sharing my configuration first. (it's nothing special)

JIRA Version: Server ver. 7.0.10

Mail Handler Server:  service_account_A@gmail.com

Handler: Create a new issue or add a comment to an existing issue.

Bulk: Ignore the email and do nothing.

Default Reporter: outsider (confirmed it has permission to create issue to the specified project ABC)

My problem is, if I send an email to the mail handler gmail account, there will be 2 different behaviors when I click the "Test" button or not to.

1. If not click and wait for mail handler automatically triggers.

    The issues will be created as expected.

2. If click Test button:

    The test result shows 1 new issue created (as follows).

Summary:

• 1 message read from the server.
• 1 new issue created.

Found 1 unprocessed message(s) in the pop3s folder.
Creating issue with summary 'TTTTTTTTTTTTTTTTTTTTTTTTTTTTTT' and reporter 'outsider'
Deleting Message 'TTTTTTTTTTTTTTTTTTTTTTTTTTTTTT'

    But as a result, I'm unable to find the created issue, also checked the "atlassian-jira-incoming-mail.log",  all looks fine but there's no log saying a new issue is created.

My question is, is it an expected behavior that issues won't be created if you enter the test mode?

(Can't find any related information...)

Thanks.

I've enabled the DEBUG log for incoming-log, below is what I got, FYR.

---------------------------------------------------------------

349 DEBUG message-handlers/test DEBUG POP3: authentication command succeeded
349 DEBUG message-handlers/test Successfully connected to mail store
349 DEBUG message-handlers/test Getting folder [INBOX]
350 DEBUG message-handlers/test Got folder [INBOX] now opening it for read/write
350 DEBUG message-handlers/test C: STAT
448 DEBUG message-handlers/test S: +OK 1 5058
448 DEBUG message-handlers/test C: NOOP
545 DEBUG message-handlers/test S: +OK
545 DEBUG message-handlers/test null[12000]: Found 1 unprocessed message(s) in the pop3s folder
545 DEBUG message-handlers/test Processing message
545 DEBUG message-handlers/test C: TOP 1 0
654 DEBUG message-handlers/test S: +OK message follows
655 DEBUG message-handlers/test Message Subject: TTTTTTTTTTTTTTTTTTTTTTTTTTTTTT
655 DEBUG message-handlers/test Message-ID: <CAJCB_M44nTjZux_ZwL0_HqwsWZ+dx8nV15sw7b7naT9SdpO0JQ@mail.gmail.com>
656 DEBUG message-handlers/test Calling handleMessage
656 DEBUG message-handlers/test Looking for Issue Key in subject 'TTTTTTTTTTTTTTTTTTTTTTTTTTTTTT'.
656 DEBUG message-handlers/test Issue Key not found in subject 'TTTTTTTTTTTTTTTTTTTTTTTTTTTTTT'. Inspecting the in-reply-to message ID.
656 DEBUG message-handlers/test No Issue found for email 'TTTTTTTTTTTTTTTTTTTTTTTTTTTTTT' - creating a new Issue.
656 DEBUG message-handlers/test CreateIssueHandler.init(params: {issuetype=3 catchemail=service_account_A@gmail.com ccwatcher=false stripquotes=true createusers=false notifyusers=false project=ABC reporteruserkey=outsider bulk=ignore ccassignee=false})
656 DEBUG message-handlers/test Defaulting to fingerprint policy of 'forward'
656 DEBUG message-handlers/test CreateIssueHandler.handleMessage
657 INFO message-handlers/test Sender(s) [it-jira-testing@company.com] not registered in JIRA. Using configured default reporter 'outsider'.
657 DEBUG message-handlers/test Project key = ABC
657 DEBUG message-handlers/test Project = Project: ABC
658 DEBUG message-handlers/test Issue Type Key = 3
658 DEBUG message-handlers/test Issue Type Object = Task
664 DEBUG message-handlers/test Delivered-To: service_account_A@gmail.com
773 DEBUG message-handlers/test S: +OK message follows
881 INFO message-handlers/test Sender(s) [it-jira-testing@company.com] not registered in JIRA. Using configured default reporter 'outsider'.
891 DEBUG message-handlers/test Adding attachments for multi-part message. Part 1 of 2.
891 DEBUG message-handlers/test Checking if attachment should be added to issue:
891 DEBUG message-handlers/test Content-Type: text/plain; charset="UTF-8"
891 DEBUG message-handlers/test Content-Disposition: null
891 DEBUG message-handlers/test Attachment detected as plain text.
891 DEBUG message-handlers/test Attachment was ignored.
891 DEBUG message-handlers/test Adding attachments for multi-part message. Part 2 of 2.
891 DEBUG message-handlers/test Checking if attachment should be added to issue:
891 DEBUG message-handlers/test Content-Type: text/html; charset="UTF-8"
891 DEBUG message-handlers/test Content-Disposition: null
891 DEBUG message-handlers/test Attachment detected as HTML.
891 DEBUG message-handlers/test Attachment was ignored.
896 DEBUG message-handlers/test Delivered-To: service_account_A@gmail.com
007 DEBUG message-handlers/test S: +OK message follows
008 DEBUG message-handlers/test Deleting Message: <CAJCB_M44nTjZux_ZwL0_HqwsWZ+dx8nV15sw7b7naT9SdpO0JQ@mail.gmail.com> (skipped due to dry-run mode)
008 DEBUG message-handlers/test Closing folder
013 DEBUG message-handlers/test Delivered-To: service_account_A@gmail.com
110 DEBUG message-handlers/test S: +OK
110 DEBUG message-handlers/test C: QUIT
364 DEBUG message-handlers/test S: +OK Farewell.
364 DEBUG message-handlers/test Closing store

[Luciano Fagundes · Accepted solution]

Hi Horace, this is an expected behavior, test mode will validate if the issue is processed and after that remove the test issue from JIRA.

[Horace Su]

Thanks!