Maher, John wrote:
Gerold: Hi John,
Thanks for your response. The links have been fixed (I was home sick yesterday and didn't check the links before I sent out the initial email: my apologies):
http://www.bol.ucla.edu/~jmaher/otrsIssue/index.html ok now
As far as upgrading goes, I'm more concerned with the cause of the problem, and I have nothing to indicate that it's specific to the version I'm running. Unfortunately we're in the middle of a major upgrade to our infrastructure that's impacting over 50,000 users and right now I just need to know what the problem is: I'm not in a position where I can afford to upgrade the application and have the problem continue. Well, 1.2.4 is a bugfixing release, and what I see in your screenshots looks strange, indeed. You clicked at Consult(30) link, did you?
My hunch is that it has something to do with how OTRS is interfacing with the data.
Right, and if that code contained a bug, which was fixed in 1.2.4? Don't know, but as cautious as I am with new versions, as open-minded I am for bugfixing releases, even if there is always the risk of getting new tiny animals.
Once again, any assistance in figuring out where the tickets went and how to get them to show up in the UI would be greatly appreciated.
If you are searching for tickets in queue custom, what do you get?
Thanks again,
your welcome
John Maher | BOL Coordinator | jmaher@cts.ucla.edu
Gerold