Iām adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. The team will revisit this bug next sprint.
This issue already fixed in 4.4+. We are not going to fix it in 4.3 unless there is a customer request attached to it. Closing it as WONTFIX.