Hey dbarkho,
Sorry I missed that you’d already logged this one, so no need to lodge another case. The item description auto expand issue affecting Quotes, Sales Orders and Invoices is officially logged with our product and engineering teams, and it’s being tracked there. We do have a public status page, though it’s used for incidents or outages that affect service availability rather than product defects like this UI regression, so it won’t show up there. On timeframe, sorry an estimate was shared earlier. That isn't something we’d normally provide for fixes of this kind because work is planned well in advance and bringing something forward usually needs to be very high priority or potentially an easy fix.
Cheers,
Doreen
Thanks, Doreen.
I appreciate the update, but the part that’s hard to reconcile is this:
This isn’t an enhancement — MYOB broke a previously working feature during a UI update.
The description field used to auto-expand.
A MYOB change removed that behaviour.
So it’s a regression caused by MYOB, not a feature request from customers.
Given that, it’s difficult to understand why:
When MYOB introduces a defect that affects every quote, invoice, and sales order, the expectation is that it’s addressed with urgency — not placed into the general backlog.
To keep things simple, can you confirm two things:
We’re not asking for miracles — just accountability for a defect introduced by an update, and some clarity on when customers can expect it to be resolved.
HI dbarkho , Doreen hasnt referred to this as an enhancement in her response.
1) Yes it is a bug/defect/regression, whatever term you wish to define it. You are correct that it is not an enhancement or feedback
2) A fix has not been scheduled
Thanks for confirming, Mike.
If it’s officially recognised as a bug/defect/regression, then the natural follow-up question is:
Why has a regression introduced by a MYOB update still not been scheduled for a fix after two months?
This isn’t a minor edge-case. It affects every invoice, quote, and sales order created by every user.
It was working, MYOB changed something, and the feature broke immediately after that update.
So the concern isn’t whether MYOB acknowledges the defect — it’s why there is zero timeline and no scheduled fix for something MYOB itself unintentionally removed.
When regressions go unscheduled indefinitely, it creates the impression that stability issues introduced by updates are not being prioritised.
Can you clarify:
Customers just want confidence that when MYOB breaks something, it is treated with urgency, not left open-ended.
Hi dbarkho ,
There are a number of variables the affect prioritisation of work for our product managers and development teams.
I'm not able to list it all out here, partly because I don't work in our product development team and have access to the 'formula', but it is also not a simple case of: this must affect x number of customers (for example).
I think you were on the right path with your original post.
Understanding what other customers are experiencing with this description field issue, how this is affecting them on a daily basis, and whether anyone else has found a workaround or solution.
As much as the number of impacted customer is not the sole determining factor, it is something that is used to help with prioritising.
