Doing Xojos job with re-verifying bugs in new Feedback

The context was that 10 year old bugs that no longer exist in features of the current version of xojo should really be closed. If by your comment you mean “this is crazy talk” then, I agree with Dana, it isn’t very nice and is also a perfectly valid point that Arnaud made.

I don’t think he was talking about you though, more like about Arnaud, oh actually, re-read, yeah you too. Naughty Rick!

1 Like

Ok. I want a refund for the recent PRO license I bought. I can go elsewhere as you wish.

Please contact hello@xojo.com to request a refund. We offer a 90 day full refund guarantee on all Xojo licenses.

2 Likes

It’s already done here. But ok, I’ll replicate your request there.

A very long discussion, after which I came away believing that the Xojo team understand Feedback needs improvement and have a genuine desire to do so. I think it’s fair to say that the MVPs pressed our case as much as we could, because we all have many of the same concerns expressed in this thread. While I won’t divulge specifically what we discussed, I’d encourage professional, constructive, helpful feedback around this issue, either here on the forum, or reach out to an MVP and I promise that you we will try to relay that in the best way we can. This conversation is not over.

7 Likes

question for Xojo
Why do you think emotions are running so high among more than a few long time customers?

4 Likes

Not sure, ask them in an email or make a new thread?

Dear MVP’s. Kindly ask Xojo to put things back the way they were until they think of a better way to go about this as it looks like they’re trying to shy away from huge lists of “Reproducible” and “Verified” tickets by not letting anyone know the current state of tickets. Thanks

8 Likes

Take for granted that we review and work in all the bug cases as fast as we can (in fact, that’s the first thing I do in the morning)

Sometimes fixing a bug takes minutes to do, other times is a “bit” more difficult to find the root of the problem and make sure that everything works as expected (including backwards compatibility); and other times it takes other pieces of the framework to be considered; other times is just about bad timing.

The summary is that ALL of your efforts reporting bugs is tremendously laudable and we are grateful for that: it reverts in a better product and to the community in general.

The change from what you were used to see to the new Open / Close thing, doesn’t mean that we are going to change that internally. I mean: we will take the same steeps on every case and put the same amount of effort on everyone of these.

Of course, it is tremendously valuable to have an example project and as many hints as you can offer in order to fix a particular bug (believe me): that speeds up the process and everyone will be happier at the end!

As many Spanish users have heard from me in the Spanish Hangouts, I alwasy push them to report to us the bugs they may find in the product, because we care about them and, of course, about you!

Just my 2 cents.

8 Likes

Nobody says you don’t because we (developers) all do basicly the same work…
The issue is more, it seems to pile up faster than being slimmed down it’s a simple as that.

It seems you have too much work to do. However it may be, it’s up to Xojo to do something to provide good service. I’m sure there is a solution somewhere on @Geoff_Perlman 's plate but we don’t have it (yet).

Well, it may be good to have all Web 1 bugs checked, whether they are still valid for Web 2.
Some are still an issue, but most probably not since the code of the controls was replaced.

1.3 million sales, 7 programmers, end users from all walks of life, support ticket selection:

image

Xojo:

You know what, why stop at where we are, surely its a little confusing? While you’re changing what people see, how about you just go from Open to Closed/Solved?

  • Open - Useful, default position for a new ticket
  • Scheduled - Pointless, doesn’t tell us when its going to be worked on, could be a week or a year as xojo doesn’t give out time scales
  • Fixed - Pointless as it hasn’t been checked yet so it could end up as Open again when a tester finds a problem with it
  • Fixed and Verified - Pointless if the user isn’t in the testers group, and as there’s no eta on releases it could be a long wait
  • Implemented - Pointless, see Fixed
  • Implemented and Verified - Pointless, see Fixed and Verified
  • Closed - Useful for keeping the numbers down.
  • Information required - Pointless, just write what we need into the ticket, it’ll be closed on the next check if they don’t see it, but at least that will give them chance to go on holiday and not close it in 10 days.
2 Likes

I’m glad to see Feedback coming to Web!
I don’t see an issue in verifying a bug is still an issue after a release in case another change fixed it.
I think the crux of the issue is that some bugs sit around for too long unresolved, which is what users are vocalising in several ways.
As a community we need to help Xojo resolve that issue rather than complaining about it.

2 Likes

Please remember the guidelines, stop the personal digs and stick to the topic or this thread will be locked.

https://forum.xojo.com/faq

3 Likes

Could you answer Karen’s question from above?

3 Likes

Hi Karen, I actually started replying to you in this thread earlier but didn’t want to help drive it further off topic. But since Mr. Heavens has specifically requested, I will say I am not dismissing your concerns or the concerns voiced by members of this forum. But when Xojo makes decisions we consider our entire userbase, a fraction of which is on this forum and an even smaller fraction of which is vocal (in the way you are implying) on this forum. Yes, we are reading this thread and are aware of the strong emotions. But our annual survey of Xojo users and renewal metrics don’t reflect your experience as that of the majority of Xojo users. We will continue to base our decisions on feedback we get from many sources, one of which is this forum. If you want to discuss this further you can reach out to me privately or start a new thread but let’s keep things on topic in this one.

9 Likes

Which blog is this?

Thanks.

I’ve thought about this for a while, my main thoughts are inline with @Beatrix_Willius and @anon20074439

Over the last 6 or so years, I’ve slowed down reporting issues and feature requests not just to Xojo, but to other companies as well.

Xojo appears to have put more attention on my issues recently, as they did notify me that they’ve completed 4 of my cases with 2021r3 (which is way better than Apple, and with a significantly less operational budget).

I find the whole Xojo 2.0 thing to be very frustrating (as Xojo staff know). Re-writing things because the Xojo language and controls were simplified for others, doesn’t bring joy, and reduces my enthusiasm.

I am in two minds about the whole bug reporting system, as I feel that the current system does not work well for those of us who’ve used the product for long time, with issues that affect only a couple of customers. I understand there needs to be triage, so I don’t know what the best solution is.

<Sigh/> I don’t get to spend as much time as I like in front of the computer at the moment (due to other obligations), I already have to work around whatever crappy issues that Apple throws in my face, replace massive chunks of the Ohanaware App Kit due to Xojo 2.0, that I’ll probably not invest much of my time into verification of outstanding issues.

I think the whole process would go easier if I could just give Xojo a handful of Important case numbers (things that I can’t workaround, or things that I feel a little elbow grease from Xojo would make it a much better product), and then flush the rest down the toilet. Sure some useful things would be lost, but I feel that is a better compromise than for me to spend hours or days going through all my open cases.

5 Likes