0022493: A new issue is sometime created when the reporter reply to email notification which include the bug id of the original issue.

ID	Project	Category	View Status	Date Submitted	Last Update
0022493	Plugin - EmailReporting	General	public	2017-03-07 16:19	2026-10-21 14:43

Reporter	claurent	Assigned To	SL-Gundam
Priority	normal	Severity	minor	Reproducibility	always
Status	resolved	Resolution	fixed
Product Version	0.9.3

Summary	0022493: A new issue is sometime created when the reporter reply to email notification which include the bug id of the original issue.
Description	Sometime when a registered user reply to a notification sent by Mantis which include the original bug id in the subject line, the email reporting tool will create a new issue as oppose to append a note to the original issue. This does not happen all the time. Sometimes it works and other time it doesn't. This is somewhat annoying as we constantly have to close out the extra bug that was created and append the note to the original issue.
Steps To Reproduce	Prerequisite: Create a user account with email address that will used to email the issue via email Steps: Using the email account from the prereq step, email an issue to the mailbox being used for the EmailReporting system Run the crob job to import the issue into Mantis Review and assign the newly created issue to a developer Expected result: An email notification is sent to the requester of the status change. Using the email account from the prereq step, reply with a note to the EmailReporting mailbox using the same notification received on step 3 Run the crob job to updated the existing issue from Mantis Expected result: The existing issue from step 2 is updated with the note sent from the email Actual result: A new bug is created with the title of the email which contains the original bug id
Tags	No tags attached.

SL-Gundam 2017-03-07 17:32 manager ~0055973	What version of MantisBT are you using?

SL-Gundam 2017-03-07 17:36 manager ~0055974	Does this describe your issue? https://www.mantisbt.org/forums/viewtopic.php?f=13&t=22623

claurent 2017-03-07 17:37 reporter ~0055975	I am using MantisBT 2.0.0 with EmailReporting 0.9.3.

SL-Gundam 2017-03-11 18:49 manager ~0056046	Still waiting on an answer for this question 0022493:0055974

claurent 2017-03-13 09:19 reporter ~0056053	Yes, my issue is somewhat related to the article about the read-only state; however, when I tried with MantisBT 2.2.0 and EmailReportin0.10.0DEV, I was not able to replicate the reported issue.

SL-Gundam 2017-03-13 12:26 reporter ~0056059 Last edited: 2017-03-13 12:45	It might be that they changed the logic for MantisBT 2.2.x Will check that out

SL-Gundam 2017-03-13 12:48 reporter ~0056060	Could not find any significant changes here. Will have to test the functionality more extensively At least good to know that the newer versions of both MantisBT and EmailReporting work better Will leave this issue open while i'm still investigating this For the moment created some documentation for this issue https://www.mantisbt.org/wiki/doku.php/mantisbt:emailreporting#readonly_threshold_for_issues

claurent 2017-03-13 13:12 reporter ~0056062	When will the EmailReporting version 0.10.X be released? Since the version we downloaded is marked as DEV, we did not deploy this to our production environment.

SL-Gundam 2017-03-13 21:16 reporter ~0056068	Current plan is to add support for the markdown feature of MantisBT 2.1.x After that EmailReporting 0.10.x should be released... This could take a couple weeks though since its seriously impacts current functioning of this plugin

View Issue Details

Activities