Versions become unsynced between manage project page and soap api calls after a few months

Hello, over the last week we've been observing a strange bug in JIRA. When creating a new project's milestones through the soap interface they no longer showed up in the browser when viewing the projects admin page. Creating a new milestone through the admin page revealed both the milestone just created and the milestone created via the soap interface, however the milestones created via the web page did not show up in the soap interface.

I should also point out that at no part of this preliminary testing did any error messages show up or anything in the xml response to indicate that the results from the API calls where inconsistent with the info on the admin page. As far as our app was concerned nothing was wrong at all until we tried to use the milestones and they didn't exist or we noticied the discrepancy verifying manually.

I tried making several milestones through both methods then deleting them all. the milestones deleted from the admin page which had been created through the soap interface still showed up in the soap calls even though they were deleted. At this point trying to create any milestone through the soap interface resulted in an error "geric entity not found". I tried explicity calling "log out" thinking that maybe something wasn't being flushed to DB, but that had no effect. restarting my app had no effect, and it still failed when I wrote a small standalone app just to check to see if a recent change in our code had caused the bug.

I dont know why it happened but we did discover that restarting jira seemed to solve the sync issue between the interface and the admin page. Restarting jira which had otherwise been running fine for ~1.5 months is a measure that we would prefer to avoid in the future.

Even though the SOAP api returned a Generic Entity Not Found exception and a few null pointer execeptions on several occasions threre were no related error messages in the logs :S sorry. I'm not sure you'll be able to reproduce this bug without logs (or waiting a few months), but at least you'll be aware that it exists.