@jeff_strater I definitely appreciate the challenges of project management. I have been a commercial/industrial construction project manager for the last twenty-seven years.
I don't mean to make your blood boil over this item specifically. But I would like to make it boil a bit over a generalization. Something a project manager learns on the very first job is that when you're behind and the customer is complaining, the most effective contributor towards rectifying the problem is usually putting more manpower on the job. Autodesk obviously has thought about the cost/reward ratio of committed resources versus development timeline, and seems content with the current pace. And certainly they do turn out product improvements on a regular and even frequent basis. But they've got to know that we users have a lackluster perception of the current pace, right?
Do they have some particular time frame regarding the completion of some more finished state? I mean, for example, that we all make the excuse for F360 - as compared to Inventor or Solidworks - that it's a lot younger so of course it isn't going to be as complete yet. Is there some future target date that Autodesk expects to reach that level of completeness? Have they estimated the amount of work to be done and divided it up over a ten year window, or a three year window, or what?
And do they divide all the Ideas into, "That would be nice," and, "Hey, this is basic functionality that ought to be done already?" Things like finishing the Joints list, and like this driven dimension deficiency, ought to be placed within the latter category, and as such ought to outweigh a lot of stuff in the first category, regardless of development ease and number of votes.
An analogy in building construction would be, "The concrete foundation is a lot more work, and nobody is ever going to appreciate its architectural beauty, but its got to be done right before we worry about picking window treatments." Know what I mean?