I administered an old version of Jira on-prem for years, but I'm new to doing this in the Cloud version. Yesterday I configured mail processing from an on-prem mailbox and it was working fine. This morning one of the people testing it told me that her e-mails weren't getting processed.
I've narrowed the issue down to the fact that the e-mail address she's sending from was configured as a "portal only customer". I've tested two other addresses:
This behavior seems backwards to me. If I were automatically creating portal only customers from incoming e-mails, this would make it so they could only ever send one ticket via e-mail (if that). What am I missing?
Thanks,
Chaz
Chaz,
What are your customer permissions set to on the service desk?
https://confluence.atlassian.com/servicedeskcloud/project-customer-permissions-954239155.html
"Customers my team adds to the project"
I'm not perfectly sure how the original affected user was added (whether they were entered manually or someone was testing auto creation), but the test users I created were definitely done manually, so I assume they qualify as "Customers my team adds to the project".
Thanks,
Chaz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Based on the article you linked (which I had already read), I just want to clarify...e-mails that are not portal only customers work just fine.
Thanks,
Chaz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What are you seeing in the service desk email processing log, what is the specific error?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I haven't been able to find a log so far. I googled and googled and it always seemed to reference the on-prem version.
Thanks,
Chaz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Each email address listed here will have a view log link that will provide you some additional information.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Right. I had found that earlier and didn't (don't?) think it's relevant, but then again, maybe I'm missing something huge here. Here's the history:
Someone (the non-processing user in question) had previously setup an address there, jpsup@company.atlassian.net, which I didn't know and which is not the way we should be going as a company. Last night I setup our on-prem mailbox under System>Incoming Mail and it worked and continues to work.
I'm not sure how the two interact, but I didn't want to go messing with that jpsup@ address if it wasn't impeding progress. Point being, there's next to nothing in that log:
Thanks,
Chaz
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.