JETI exception while processing an incoming email

I get the below message when I try to configure Email This Issue Mail Handler for a project/issue type combination for which I've defined a mail handler. What could be the cause of this error? What am I doing wrong?

JIRA 6 / JETI 5.4.1

Exception: key should not be null!: key should not be null!

2 answers

In our company we are having the same issue. 2015-09-22 15:31:01,537 atlassian-scheduler-quartz1.clustered_Worker-2 ERROR anonymous ECS Mail Handler [atlassian.mail.incoming.mailfetcherservice] ECS Mail Handler[10040]: Exception: key should not be null! com.atlassian.jira.util.dbc.Assertions$NullArgumentException: key should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull( Have you been able to fix the error? JIRA 6.4.8 / JETI

+1 - we have the same issue.

Perfect error reporting! :-/

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,237 views 14 19
Join discussion

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