Email This Issue' ver 5.5.0.10 intermittently using wrong Handler.

Hi,

I have installed 'Email This Issue' version 5.5.0.10 on JIRA 6.3.9.

My 'Knownuser' is sometimes mapped to the wrong project. You can see from the logs the 'Knownuser' is correctly mapped to the INTERNAL Project, then the 'Knwonuser' is incorrectly mapped to the SUPPORT Project.

The below logs show two users creating Issues by email.

The expected results are 'Knownuser' is mapped to the INTERNAL Project, any unknown users are mapped to the SUPPORT Project as 'remoteuser'.

You can see at 19:10:43,129 and 19:13:43,254 the INTERNAL HANDLER correctly recognises the 'Knownuser' and creates the Issues in the INTERNAL Project.

Then… at 19:16:03 the 'Knownuser' is incorrectly mapped to the SUPPORT Project - this is unexpected behaviours.

What would cause this?

2014-12-20 19:10:43,129 atlassian-scheduler-quartz1.clustered_Worker-4 INFO Knownuser INTERNAL HANDLER [atlassian.mail.incoming.mailfetcherservice] INTERNAL HANDLER[10100]: Issue INTERNAL-147 created
2014-12-20 19:12:03,774 atlassian-scheduler-quartz1.clustered_Worker-4 INFO ServiceRunner SUPPORT HANDLER [mail.incoming.ReporterResolvingCreateOrCommentHandler.3] Sender(s) [unknownuser@hotmail.com] not registered in JIRA. Using configured default reporter 'remoteuser'.
2014-12-20 19:12:03,838 atlassian-scheduler-quartz1.clustered_Worker-4 INFO ServiceRunner SUPPORT HANDLER [atlassian.mail.incoming.mailfetcherservice] SUPPORT HANDLER[10100]: Issue SUPPORT-334 created
2014-12-20 19:12:03,844 atlassian-scheduler-quartz1.clustered_Worker-4 INFO ServiceRunner SUPPORT HANDLER [mail.incoming.ReporterResolvingCreateOrCommentHandler.3] Sender(s) [unknownuser@hotmail.com] not registered in JIRA. Using configured default reporter 'remoteuser'.
2014-12-20 19:13:03,972 atlassian-scheduler-quartz1.clustered_Worker-1 INFO ServiceRunner SUPPORT HANDLER [mail.incoming.ReporterResolvingCreateOrCommentHandler.3] Sender(s) [unknownuser@hotmail.com] not registered in JIRA. Using configured default reporter 'remoteuser'.
2014-12-20 19:13:04,039 atlassian-scheduler-quartz1.clustered_Worker-1 INFO ServiceRunner SUPPORT HANDLER [atlassian.mail.incoming.mailfetcherservice] SUPPORT HANDLER[10100]: Issue SUPPORT-335 created
2014-12-20 19:13:04,045 atlassian-scheduler-quartz1.clustered_Worker-1 INFO ServiceRunner SUPPORT HANDLER [mail.incoming.ReporterResolvingCreateOrCommentHandler.3] Sender(s) [unknownuser@hotmail.com] not registered in JIRA. Using configured default reporter 'remoteuser'.
2014-12-20 19:13:43,254 atlassian-scheduler-quartz1.clustered_Worker-4 INFO Knownuser INTERNAL HANDLER [atlassian.mail.incoming.mailfetcherservice] INTERNAL HANDLER[10100]: Issue INTERNAL-148 created
2014-12-20 19:16:03,771 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner SUPPORT HANDLER [mail.incoming.ReporterResolvingCreateOrCommentHandler.3] Sender(s) [unknownuser@hotmail.com] not registered in JIRA. Using configured default reporter 'remoteuser'.
2014-12-20 19:16:03,837 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner SUPPORT HANDLER [atlassian.mail.incoming.mailfetcherservice] SUPPORT HANDLER[10100]: Issue SUPPORT-336 created
2014-12-20 19:16:03,843 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner SUPPORT HANDLER [mail.incoming.ReporterResolvingCreateOrCommentHandler.3] Sender(s) [unknownuser@hotmail.com] not registered in JIRA. Using configured default reporter 'remoteuser'.
2014-12-20 19:16:03,897 atlassian-scheduler-quartz1.clustered_Worker-2 INFO Knownuser SUPPORT HANDLER [mail.incoming.ReporterResolvingCreateOrCommentHandler.3] Sender(s) [knownuser@gmail.com] not registered in JIRA. Using configured default reporter 'remoteuser'.
2014-12-20 19:16:03,976 atlassian-scheduler-quartz1.clustered_Worker-2 INFO Knownuser SUPPORT HANDLER [atlassian.mail.incoming.mailfetcherservice] SUPPORT HANDLER[10100]: Issue SUPPORT-337 created
2014-12-20 19:16:03,982 atlassian-scheduler-quartz1.clustered_Worker-2 INFO Knownuser SUPPORT HANDLER [mail.incoming.ReporterResolvingCreateOrCommentHandler.3] Sender(s) [knownuser@gmail.com] not registered in JIRA. Using configured default reporter 'remoteuser'.

I have two 'Email This Issue' handlers:

SUPPORT HANDLER - using the SUPPORT PROJECT with 'remoteuser' set as the default reporter.
INTERNAL HANDLER - using the INTERNAL PROJECT with 'Knownuser' set as the default reporter.

I would like non-JIRA users mapped to the SUPPORT Project and receive a 'We have received your mail' reply email. Our Support Staff will then manually create the user as required and move the Issue to the required Project.
I would like all known JIRA users to receive the standard JIRA notifications as normal.

I am 99% there, I just can't figure out the above problem.

It should be pointed out my Test Setup is running HSQL 1.8.0. Which I understand is technically unsupported. Could this be related to the above issues (sorry if that's a dumb question). 

Thanks,

Tim

2 answers

This widget could not be displayed.

I have since moved from HSQL database to Postgres. I still have the same problem. 

Database Version : PostgreSQL - 9.3.5
Database Driver : PostgreSQL Native Driver - PostgreSQL 9.0 JDBC4 (build 801)
This widget could not be displayed.

Tim, you should contact the plugin developers directly via http://www.meta-inf.hu/wiki/display/en/Contact 

Your chances to get a quick answer is better than here. They are nice gentlemen, I'm sure they will help you fast, even if the holiday season is coming...

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

79 views 0 1
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