Question

Hi,

We have a problem with our FogBugz installation where some categories of cases can no longer be closed or resolved. We are using Fogbugz 6.1.44.

At some point in time someone here has modified the categories in our Fogbugz Database, but I'm not sure if this is to blame for the problems closing cases. Whatever changes were made are before my time working here, so I don't know exactly what was done but I can provide database schema if it would be helpful. Our Category list is as follows; Bug, Feature, Enhancement, FAQ, Schedule Item. The two categories that can be closed and are working properly are Bug and Schedule Item, none of the other categories can be closed.

The behaviour of the problem is as follows: If you create a new case in Fogbugz of one of the affected categories, e.g. "Enhancement". the case will be added successfully. If you then view the case and choose the "Resolve" option, the Resolve case page will load but there is a warning message displayed "Confirm Navigation - If you leave now, your changes will be lost" with the options "Leave this page" or "Stay on this page". This is not correct because we are arriving at the page and not trying to leave it at this point. Normally this message would appear if you try to navigate away while editing a case, to prevent loss of changes. Also regardless of the option you choose, leave/stay. If either option is clicked they have the same result, you stay on the same page. The page is displayed how it would normally look when resolving a case, "Resolve & Close" "Resolve" and "Cancel" are the options and there is an editbox to write a comment. The problem is that if either resolve option is used the changes are not saved, e.g. If I make a comment then click "Resolve & Close" the page loads the case again displaying it still as open status and the changes have not been saved.

Has anyone had any similar problems before? Or does anyone have a suggestion on things to check.

I have had a look around through the DB tables for any obvious discrepancies, referring to the 6.0 DB schema documentation for table and field descriptions etc but didn't identify anything that was out of place.

Do you think upgrading to version 7 would possibly fix this issue?

Any suggestions are appreciated.

Answer 1

This was the product of some missing data in the Status table. We were able to massage it back into place.

Answer 2

Upgrading to FogBugz 7 would give you the ability to use the Custom Workflow Plugin which provides a supported route for customizing categories/statuses/etc.

That being said, there would likely still be problems with the data in your database that would need to be worked out. It's difficult to diagnose these kinds of problems without inspecting your actual data though, so you would likely need to email us at customer-service@fogcreek.com.