I wanted to add that the sub-project I'm trying to move the bug to does not have the same category name as the sub-project I'm moving from.

So the question now becomes, how to move a bug from one sub-project/category combination to another sub-project/category when the categories between sub-projects are different. My first inclination is to have the person moving the bug select both the "Move To" sub-project AND the "Move To" category.

Another thing I noticed is that this problem only occurs when the General Category (id 1) doesn't exist. This is the case for me as I deleted all the general categories. I updated the database table mantis_category_table and inserted id 1 with a name of General and was able to get past the message when moving a bug. The SQL I used was: INSERT INTO mantis.mantis_category_table (id, project_id, user_id, name, status) VALUES ('1', '0', '0', 'General', '0');

I still maintain my comment in the prior note: 0014189:0031714
So the question now becomes, how to move a bug from one sub-project/category combination to another sub-project/category when the categories between sub-projects are different. My first inclination is to have the person moving the bug select both the "Move To" sub-project AND the "Move To" category.

You have to define $g_default_category_for_moves to some valid category. This can be done fot all projects in config_inc.php or per project on manage configuration page.

yeah, that's how I ended up fixing the problem. I added back the general category with id 1 (effectively defining $g_default_category_for_moves).

I'd like to see an enhancement made that would give you the opportunity to select both the Project/subproject and the category when doing a move so that it doesn't require any preconfiguration in the config_inc.php or at the project level.

The original issue is a duplicate of 0013850, and atrol provided the correct fix for that. I will document this in the Admin guide / troubleshooting section.

Your feature request will be tracked separately in 0014190.