Email Requests in Service Desk not working (v2)

HELP!

 

I've read through this similar (recent) post, but emails into Service Desk have just stopped for my org. Anyone else know of recent changed/settings to check?

https://community.atlassian.com/t5/Jira-Service-Desk-questions/Email-Requests-in-Service-Desk-not-working/qaq-p/625134#U638916

Note: This was setup and working months ago. It only recently stopped. I have not changed any settings. 

Our email domain is the one that atlassian provides (***@[mycompany].atlassian.net) - so it shouldn't be related to the recent 'external' email domain changes -- detailed here: https://confluence.atlassian.com/adminjiracloud/configuring-jira-cloud-to-send-emails-on-behalf-of-your-domain-900996548.html

*Note - we are g-suite authenticated

I've tried manually adjusting permissions to give 'Service Desk Customers' the create issues permission, but that throws a Major error as described here: https://confluence.atlassian.com/jirakb/resolving-permission-scheme-errors-838416389.html  (I follow the prompts to reset it back to normal.)

My customer permissions as wide-open as showing here: Screen Shot 2017-09-12 at 2.42.36 PM.png

Screen Shot 2017-09-12 at 2.42.36 PM.png

1 answer

1 accepted

 

Figured it out. The Project Lead was changed (due to a employee termination) but all the issues types were still specifically assigned to the terminated (now inactive) user.

So the resolution was to change all the issue types to being assigned specifically to a different user.

For anyone else out there that has employees change... there is a nice log located in Configure>Appliations>Jira Service Desk>Email Requests> then click on the 'View Log' link next to the email address for your service desk> and then click the Tab for 'Processing Log'. Anything that has failed will show up there with a reason for the error.

 

In future -- I'd love to find out if I can set functionality to:

- Still create the ticket, but be unable to assign it. (Can that be done?)

- Have issues be assigned to the Project Lead rather than choosing a specific user

 

This helped. I then hit test on our email address list and found the problem.

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

247 views 0 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot