Originally Posted by ENTERPRISE
Indeed, some of it comes down to prioritization. While the uploader issue was definitely an annoying one, it was not 100% consistently failing at all times. With this in mind it was a of a lower priority but was still being researched, again to further exacerbate issues it was happening during closed office hours at the Devs end which made it hard to track. 2 Of our developers actually stayed up late through the early hours of the morning to track the issue, it was only then that they were able to identify anything which is odd as usually speaking this type off issue you would usually expect to find the cause somewhat easier than they did.
Issues can be unique and only people at ground zero who are familiar with the software are in the know. You can consult as many developers as you want, but unless they are familiar with the software or are at ground zero...they are not in a position to really evaluate the situation.
Alas, the delay in finding the fix can be attributed to a a couple of factors as indicated. It was annoying and frustrating for all and we can appreciate that.
The good thing is that we are on to it now
I hear an echo.
My statement seems to be spot on. After doing little or nothing, developers monitored the system during the hours issue was happening an identified it.
My reference to consulting others was in reference to removed or changed post with no history of the changes. All readily agreed it was indeed generally not a big deal to do this at their access level .. in other words I most likely did not imagine it happened, but t actually did happen.
I can understand not aggressively addressing the problem, but spending a month covering it up by saying it was being hard to find is total garbage. All it took was a developer or two spending the time looking for the problem during the time of day it was occurring and you know know it is for real. The fact this was not done for a month while posting up it was being worked on is what I feel was poor handling of the problem. It shows a very poor response by developer to a problem, even if it was not a big problem to most users on earth. In the beginning all we (the users experiencing the problem) wanted was for it to be acknowledged as at least a possible issue, something the the huddlers did not do when it was first reported. This was compounded by a month of being 'patted on the head' and told it was being looked into with statements like
"Seeing as how we're chasing an intermittent problem (as many support posts stated), it's difficult to reproduce on demand, which is what our devs need to fix it."
But doing it at times it was not happeining .. and never doing it during the time frame it was happening in .. while we (the users experiencing the problem) knew for sure it was happening every day during the time frame we kept saying it was happening. .. and only then (a month later) was it really looked at and found .. in the first 6 hour period developers finally monitored it in the time frame it was occurring and finding the issue.
So why were we told it was being 'worked on' when it was not? Why did it take a month of these 'miss-information' posts about it being worked on before it was actually looked at?
I for one feel we were strung along. That this 'miss-information' we were told is offensive. That we deserved to know it was not being worked on instead of being placated with 'miss'information'.
I can accept the developers being too busy to address the problem.
I do not accept being treated the way we were.
Respect is a two way street, and I do not feel this two way respect was exercised here.