We did buy it and it is working fine...bought it on August 24th. It got rid of an error we sometimes got that it wasn't able to send an email through, but the email went through anyway. There were a couple of other things I can't recall. I also have had some luck chatting with tech support from the main Bugify website.
With all the spam that took over the discussion, I wonder if it wasn't just convenient to cull most posts. I don't know.
As for whether it was worth it...it was, in the sense that it didn't break anything, fixed some bugs and made us feel we're not using abandon-ware. If these subscriptions fuel a worthy 2.0 release then it is worth it...if it's just sunken costs, then it's more debatable. We find Bugify useful and especially so for its simplicity for many of our non-programming techs, so it would be unfortunate to have to switch if it fell by the wayside. I tell myself that hopefully the new owners are working on a 2.0 and that's what we funded.
since my installation is for use by condominium community property - which is a non-profit - Robert gave me a discount to buy it at half price - $35 i think.
and its been hard to keep the board of directors and property management motivated to use it -- which I cant fathom why they are so reluctant, since Bugify is a great system! Especially for continuity, record keeping and historical management (especially with all the customization/changes I did to it)
anyway, i tried explaining this to the new owner via that "chat" session - which he answered at the time - either he didnt understand or didnt care that we are a non-profit - so he wasnt going to give me a break on the update cost.
thats why i find it hard to fork over $50 when it cost me $35 to buy in first place - for a system that may be abandon, by my users, sometime in the future anyway.
though i do have to admit - the email reply facility would make my instance even far more useful and convenient.
Can't speak for the owner, but it's possible they were reluctant to give a price-break without knowing what their income baseline would be. Might have just been too early in their cycle to know if they should do that sort of thing for you, or who you were (you seem to have had many contributions over the years on Bugify). Maybe try them again?
Your problem with getting "those people" to use Bugify are not unique. I can not for the life of me understand the reluctance people have for documenting/tracking issues. With our heavy data and program driven techs using Bugify is a no-brainer. 100% buy-in. Everyone loves it for those reasons...permanence, references, continuity, management, fewer loose ends etc. For everyone else it's like pulling teeth. Even if I go as far as asking them to just tell me the info and I'll start an issue for it and then they just have to update it, it seems to be impossible. Even if 90% of the issue is resolved and all they have to do is confirm the solution and mark the issue as resolved or closed, it seems to be impossible. I can only assume they are being lazy because there is 0 other compelling reason to not do this extremely useful things. Our projects have 10, 15, 20 year lifespans so knowing what went on years ago is extremely useful. I hope you find the magic potion because I fully support your effort, spiritually :)
Back to the cost....I mean, obviously you either have the money or not, but if you do, I wouldn't feel to awful gambling $50 and finding out it only takes you forward another 6-12 months...and maybe you'll get the email reply feature.