I think this is an issue with product management and design. I remember all of the requests for this feature and that gizmo...a whole bunch of 'wouldn't it be nice if...' requests. This is all good for gauging the sort of things that players are looking for. However, as a product manager or designer you don't say yes to everything. Sure the idea of a stadium editor sounds like a great feature for a small percentage of users but what impact does this have on product stability, development resource focus, user experience, etc. and did the stadium editor result in any extra sales? That is just one example but you can see all of this accretion of poorly evaluated features across the game and yet fundamental issues go unaddressed and important components (DRS) get removed (yes, I know it is still 'in the game' but it is essentially turned off for AI...it's certainly significantly downgraded from DBC14).
What BA should be doing is focusing on the one thing that all users want...the core mechanics of a cricket game that looks and feels like cricket. Once this works and is delivering the right experience to the majority of customers, then they can look to add in new features (as long as the are properly evaluated as enhancing the game for the majority of players rather than adding to its complexity to serve an edge case). I would quite happily buy supported DLC (stadiums, player likenesses, umpires, kits, etc.) rather than having to muddle through the complexity of the current game and its myriad customisations...if, that is, the core game engine delivered a good cricket experience.
All that said, I do appreciate the work and effort that BA have put into cricket games and know that it is far easier to chip in with opinions from the sidelines than it is to create a great game. I've put a lot of hours into the trilogy and am still enjoying Ashes. I just know, as I suppose we all do, that Ashes seems so close to being great but is let down by failing to do the cricketing basics on too many occasions. I still contend that this is a product management and design issue and not one of coding or testing.