Mantis Bug Tracker - Forums

Hi,

I am using email reporting plugin,
How do i change the status of the bug when i add note for bug via email ?

Note: Mantis send me email , and i reply a note via email, but status not change.

Thanks

With MantisBT 1.2.x this still worked but ever since i upgraded to MantisBT 1.3.x status changes are no longer happening.

MantisBT 1.3.x moved to relevant code from the bugnote_add function to the bugnote_add.php file
Which means EmailReporting will have to copy the necessary code to make this work

This should be fixed now

https://github.com/mantisbt-plugins/Ema ... 613f743eff

Thanks but I did what you write , the note comes to bog note part, but the status not changed,

I want to change the status when added a bugnote via email

There are 2 moments MantisBT/EmailReporting does an automatic status change

• When an issue has the feedback status and the reporter adds a note while he is not the one handling the issue but there is a user assigned to the issue (reassign_on_feedback must be ON)
• When an issue is resolved and an email is added to the issue. This will reopen the issue and give it the feedback status (bug_reopen_status)

The first one was not working in MantisBT 1.3.x until it was fixed here: http://www.mantisbt.org/forums/viewtopi ... 753#p60753

Was this what you meant?

In my configuration reassign_on_feedback is ON it is OK,
the status changes when a bugnote added to issue, it is OK,

But my problem is.
I mean ;
An issue has a status of feedback,
An email send to the reporter for "add bugnote please for your isssue",

But user not opens the issue from his account ,
User replys by email (outlook,hotmail etc.)
The bugnote is added to that issue. it is OK
But the status not changes it is again FEEDBACK

I want to change the status of this issue as ASSIGNED

Which version of EmailReporting are you currently running because, like i said, this should fix it
https://github.com/mantisbt-plugins/Ema ... 613f743eff

This fix is in 0.9.3-DEV

The Last Log like below , i should upgrade it to 0.9.3 OK ?

Bu the latest release is 0.9.2 where can i download 0.9.3.
https://github.com/mantisbt-plugins/Ema ... g/releases

Changelog:
Jul 2016 - EmailReporting-0.9.2
- Fixed collation check issue with MantisBT 1.3.x
- Modified the user option list to also check user accessible projects
- Show missing user id behind the error in the user option list
- user_is_realname_valid function does not exist in MantisBT 1.3.x
- Changed errors formatting
- Added current mailbox runtime in seconds to debug mode when show memory usage is enabled
- Fixed PHP7 removed functionality in pear package mimeDecode
- Fixed notice level error in pear package mimeDecode

Go here: https://github.com/mantisbt-plugins/EmailReporting
Click on "Clone or download"
Click on "Download ZIP"

Make sure the contents of this ZIP file overwrite the existing EmailReporting files and you should be good to go

Thanks i will tray

We upgrade the plugin Email Reporting 0.9.3
And Upgrade mantis Core 2.0

there is no line like below in config_defaults.inc.php

$t_bug_data = new BugData;
+ // MantisBT 1.3.x function
+ if ( method_exists( $t_bug_data, 'process_mentions' ) )
+ {
+ $t_bug_data->process_mentions();
+ }

So the isssue not works , should i add these lines to config_defaults.inc.php

no that code should not be config_defaults.inc.php

Are your getting an error?
Try explaining what you expect to happen and what actually happens

I mean ;
An issue has a status of feedback,
An email send to the reporter for "add bugnote please for your isssue",

But user not opens the issue from his mantis account ,
User REPLYs by email (outlook,hotmail etc.)
The bugnote is added to that issue. it is OK
But the status not changes, it is again FEEDBACK

I want to change the status of this issue as ASSIGNED, when the user answers via email REPLY

To my knowledge we fixed that issue in 0.9.3. I can't find a single reason why MantisBT 2.0.0 would break this again

I'm wondering what caused this post though: viewtopic.php?p=61119#p61119
And its relation to the current issue
If there is an error i would very much like to see it