Michael Bauer

I'm afraid this this still not been addressed... obviously. It should have been but seems to have been dropped, probably because of other priorities at the time.  As a problem in itself it doesn't have a very high priority, although I appreciate the way you view this.  I have raised this again with the dev team to see if we can get it planned in and addressed once and for all.  Will update you when I know more.  Same bug number CRQ-6274.

2 months seems a more than reasonable amount of time for *some* form of feedback...

Michael Bauer

Michael Bauer said:

2 months seems a more than reasonable amount of time for *some* form of feedback...

Currently the only comment is that thanks to you raising this it has been kept on the radar for a future CU.  But i's currently tagged as a trivial issue which means it won't get looked at as a high priority item and has not been planned in at all.

I'll update you when if the situation changes.

A "trivial" issue that will get looked at when the devs are bored with developing new features nobody asked for ... gee, thanks Trados, that makes me feel really good about using your products, knowing you got my back on usability ... I know what I'll be saying next time someone asks me "Studio or MemoQ" ...

Michael Bauer

No... a trivial issue that will get looked at when more important bugs have been addressed. There has to be a way to categorise things and I can either keep stalling you, or tell you the truth.

All software companies will work the same way. We currently have a priority this year to really address as many of the top two categories of open issues we have logged. This one is not in the top two categories so it may not get addressed quickly unless it happens to fall within an area where we can easily address it while working on something else.

Michael Bauer

No... a trivial issue that will get looked at when more important bugs have been addressed. There has to be a way to categorise things and I can either keep stalling you, or tell you the truth.

All software companies will work the same way. We currently have a priority this year to really address as many of the top two categories of open issues we have logged. This one is not in the top two categories so it may not get addressed quickly unless it happens to fall within an area where we can easily address it while working on something else.

I know you're just relaying this and I appreciate you looking into this. What's bugging me (pardon the pun) is your organisation's approach to usability issues, not you personally .

If this was a new bug, I could accept that categorisation. But I logged this issue 4 years ago. If 4 years on a user has to chase a usability issue to find out it's in the "trivial" category, that gives one ZERO hope that it will get fixed before I retire...

Hi Paul

So how's my "trivial" issue doing?