Mail handler does not process comments. But new tickets are ok

[Alex Kolesov]

Dear community, can you please help me with my issue?

What do I have:

1. JSM with Exchange online (Exo) mail account set up as Reply-to address and Connected email account with set up Request Type for my Helpdesk project
2. Exo mailbox set up as an incoming mail server (same, as from p1)
3. Mail handler for my Helpdesk project with the same account set up as
   1. Create a new issue or add a comment to an existing issue
   2. 1 min delay
   3. Default inbox config
   4. No catch email address, no forward email, no default reporter
   5. Bulk = ignore
4. Global configuration for Email is set to "Yes, allow all emails that contain a valid issue key to be added as a comment to the issue"
5. Allow customers to create accounts on the Customer access page = true
6. Channel Access = Open

Issue:

When I send any reply to the ticket, which should be processed as a comment - nothing happens. When a new email is sent - a new ticket is created with no issues.

Debugging:

I played around with many settings and tried to test the handler, while there was an unprocessed email in Exo inbox - it reported that the email was recognized as a comment to XX issue. But it was not processed in the end. Log is clear - no "comment added" event.

I'm frustrated, as it was working well at some point and I might change smth, which is not obvious for me in JSM and now.. well, it stopped working :(

The documentation is very basic and just lists the fields to be filled. Can someone please tell me what I should set up to fix the issue with comments?

Very much appreciate for any help.

[Alex Kolesov · Accepted solution]

The solution was found with the help of Support. And it was a very big surprise for me...

In short, JSM has its built-in mail handler, which you can set up in the Connected email accounts section in JSM project settings. The Handler in Global Settings is used by other products.

[Sebastian Krzewiński]

Hi @Alex Kolesov 

Please submit support ticket to Atlassian. Support have access to logs so they will be able to check more than you.

Regards,

Seba