Doughy wrote:I called the church support desk yesterday and reported this problem directly to IT. Hopefully they have already fixed the problem. I'll follow up on my ticket number in a few days and report back what they tell me.
Techgy wrote:The service desk is VERY good at getting back to someone - at least that's been my experience.
zaneclark wrote: I eagerly await the forthcoming "new and improved" LUWS update.....
AileneRHerrick wrote:Doughy, have you heard anything back yet? We're all gripping our seats!!!
Not to throw cold water on this issue, but it seems that there is some unrealistic optimism regarding the speed with which this issue might get fixed. It's an important issue, and I also hope that it will be addressed "soon". I have no personal knowledge of the Church's development process for this project other than what I read on this forum, so the following is simply based on my opinion and decades of experience as a software developer.
Although getting a response from the service desk may happen relatively quickly, identifying the actual problem, duplicating it consistently, fixing it in the code, testing it thoroughly, and then deploying the fix is not going to happen in a matter of days, which seems to be the expectation here. That process could easily take weeks, and depending on where it fits in the list of priorities and particular release schedules, could even take months.
It may be that the issue won't be addressed at all in LUWS 1.0, but will be pushed off to LUWS 2.0, which has no announced release date. So I would recommend patience while you wait for the fix, and if you are experiencing the problems detailed in this thread, that you consider some of the alternate workarounds suggested in this thread.