Mantis Bug Tracker - Forums

Hi all,

Some coworkers did the following:
- created a new project ("Foo")
- moved some existing issues into the new project
- confirmed in 'view issues' that the issues were there
- made the new project ("Foo") a subproject of another project ("Bar")

Then all the issues that were members of "Foo" are gone. Even trying to access them by their issue number gives "application error #1100".

We tried to reproduce this on a test server, but could not. As best as they remember, we did the same as they had on the production server.

Does error #1100 mean the issues are truly deleted? or are they maybe just inaccessible somehow? How could I tell? I'm using MySQL 8.0.25 and mantis 2.25.2.

Thanks,

Sean

Check your database.
With standard settings you can run a statement like the following one in mysql command line or a tool like phpMyAdmin

Thanks so much, that was helpful! It confirms the issues in question are definitely deleted. Now, is there any way I can determine how/why/when they were deleted? Do mantis or mysql log such things?

Database logging in Mantis is deactivated out of the box, see option $g_log_level
https://mantisbt.org/docs/master/en-US/ ... ig.logging

Statement logging in MySQL is typically also not enabled.

You might be able to reproduce the workflow by checking your web server logs.

OK thanks, I'll check those avenues.

So I have a mysql dump from some time ago that contains the deleted issues, and I have a test server I can copy-paste the text and attachments out of, but if I recreate the issues on the production server they will of course have different numbers. Is there a way to edit an issue's number? Even if I have to drop down to mysql?

Tweaking the database is certainly possible, but you have to be aware of the related tables where the id is used.
https://www.mantisbt.org/docs/erd/latest.pdf