We are trialing JSM and struggling with consistent email handling. Ironically, this was a primary driver for selecting JSM, and ongoing unreliability of email processing is the factor keeping us from moving to a paid plan.
In short, JSM is marking emails as read, but does not process them. Marking the email as unread manually in a mail client causes JSM to process the email as expected.
More detail, and things we tried already:
Hi JB,
Why are you not just using the internal email that comes with JSM?
Because that email's ugly, and we don't want our highly non-technical users to have to remember the address. Some of our employees access email in ways that are not compatible with address book solutions.
We experimented with and experienced difficulty getting fwd/alias/redirect to work reliably for the full create/reply/update/close/reopen/close workflow. When we encountered the reply-to bug with MS 365 we went all-in on using the "real" email address.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you explored the External email address here:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, we have configured the external emails per those and related instructions. The email processing logs I mention are those referenced on that page.
Note that both ticket creation and update are working at least intermittently. When they do not work, JSM marks emails as read but does not process them. Marking the email as unread (and changing nothing in JSM) will consistently (So far 100% of the time) cause Jira to process it successfully.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.