Mantis Bug Tracker - Forums

While that is correct, there were 2 pull requests which concerned these issues which are related to PHP 8.3 compatibility
The necessary changes were incorporated in EmailReporting 0.11.0-DEV

The Pull requests
https://github.com/Elephant418/Markdownify/pull/48
https://github.com/Elephant418 ...

This was fixed here: https://github.com/mantisbt-plugins/Ema ... 7d377ae511

I suggest updating to EmailReporting 0.11.0-DEV
Go here: https://github.com/mantisbt-plugins/EmailReporting
Click on "<> code" and "download zip"

Good to hear. Keep in mind that for the newer MantisBT versions that EmailReporting 0.11.0-DEV is required for everything to work properly.

Could be. I believe 1.19 was from before the plugin system.
Let us know if you encounter any other issues.

If that was the solution then thats good.
Still can't figure out how the problem was created.

sidenote: mantis_emailreporting_mailbox_table and mantis_emailreporting_msg_table have never existed i believe. Did you use a fork of EmailReporting with unknown modifications?

Which version of EmailReporting are you trying to install?
Please try the latest 0.11.0-DEV version.

For notes it does not matter on which email address it is received. That only matters for new tickets.

A ticket id not unique to a project. It is unique for a MantisBT installation. So if a note is matched to a ticket, it will match it across the whole MantisBT installation. Thats is why projects and the sender/receiver email account do not matter for notes.

You might still need to run the upgrade script for MantisBT.
MantisBT made a change with categories. This causes that all categories are disabled if the upgrade script is not run.
Please check to see whether you have a existing and enabled global category in MantisBT.

ps. sorry for the late reply ...

Assuming you're running the latest version of MantisBT and EmailReporting, just setup a another mailbox the same way you did the first one.
Notes do not matter on what emailaccount them come in. This only matters for new tickets.

Good to hear.
Thanks for reporting this issue.

I suggest keeping all the indexes intact for "Classify bug priorities". This is because different email programs will use different values for priority.

A change from 2022 caused this issue.
Should be fixed now.
https://github.com/mantisbt-plugins/Ema ... 55b0a45660

Sidenote. EmailReporting only checks the priority field, not the importance field.

I'm having the same issue.
Will debug it and get back to you.

I suggest checking the other plugins that are active.
But good to hear that it's likely not EmailReporting thats the cause.

If that changes please let us know here.