[identity profile] manuka.livejournal.com posting in [community profile] techrecovery
For the last 9 months or so, we've been gestating our new church management system, and finally gave birth to a healthy application this past Tuesday. Because the new application still requires some components to be developed, portions of the legacy application will still be used for a while (such as our accounting)

This has been widely publicized to the staff, hyped, trained, and generally beaten to death. On tuesday at noon (as announced), we administered general anesthesia to the legacy app and performed a lobotomy that locked out everyone from the portions of the application that were no longer to be used (which was darn near everything). at 2:30, we brought it out of its IT-induced coma and told everyone that the new app was up and running, and had a launch party with ice cream sundaes. A good time was had by all, and everyone was excited about the new app, because the old app simply sucked that badly.

The cutover has been generally smooth, the support hotline rang only once today (yay!), and most folks are easing into the new way of doing things quite nicely (although our ticket load for other stuff is climbing rather rapidly)

And then, just as the day is ending, we get a new ticket alert:

11997 - Need information to access $legacy_app.
Description:
I am not able to access $legacy_app. I don't know if I have forgotten my login name and password or what? I think it use to automatically connect..? Could you please let me know what my information is to access it? Thanks.


My boss about hit the roof. He's going to escalate that one to her director. I suggested we merely close the ticket with "application functioning as designed, contacted facilities about removal of the rock you've been hiding under for the last 9 months."

Date: 2008-05-10 02:33 am (UTC)
From: [identity profile] lightforce.livejournal.com
Wow! That's taking "willful ignorance" to a whole new level.

I can sympathize. When I worked in the computer labs at the university I attend, we had problems like this quite frequently. Never anything quite so infuriating, though.

Date: 2008-05-12 02:01 pm (UTC)
From: [identity profile] mattcaron.livejournal.com
church management system

I am unfamiliar with this concept. What part of a church needs to be managed aside from event planning and financials both of which have a pile of applications which serve this need? I'm not busing balls, I'm genuinely intrigued.

Date: 2008-05-12 05:05 pm (UTC)
From: [identity profile] mattcaron.livejournal.com
I don't suppose you care to expand on that any more?

Date: 2008-05-15 02:40 am (UTC)
From: [identity profile] mattcaron.livejournal.com
Nifty. Thanks for explaining.

Date: 2008-05-13 10:32 pm (UTC)
From: [identity profile] theemerged.livejournal.com
Would that be the Rock of Ages, perchance?

Sorry, couldn't resist...

Profile

techrecovery: (Default)
Elitist Computer Nerd Posse

April 2017

S M T W T F S
      1
2345678
91011121314 15
16171819202122
23242526272829
30      

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Mar. 20th, 2026 12:52 am
Powered by Dreamwidth Studios