Hey @sfox2WMDD,
There is not set in stone process for determining the current status of an issue, so typically the best thing you can do is to leave another comment in the thread where the bug was reported and ask the employee who helped you for an update.
In terms of bug communication, we usually write about the biggest customer-reported bug fixes in the What's New post, and then we'll also leave a list of ALL customer-reported issues in the README post on the Support forum every release. As you can see there, although it may not always feel like it, we fix a lot of bugs with every release. I completely understand your opinion that you'd prefer for us to use our development resources "for debugging instead of implementing new features," and I can promise you that we do spend a significant mount of our time on bugs, technical debt items, and other stability issues. That being said, we strive to strike the balance between targeting impactful bugs while also continuing to build out Fusion with all tools our users need to get their jobs done.
Now regarding the bug mentioned in this post, it is something that we've begun looking at but have not nailed down the root cause yet. Given the amount of time it takes to prioritize, diagnose, fix, and then test the fix, often times bug fixes do not end up in the product for several months after being reported. Ideally we are faster than that in many cases, but once we integrate all our updated code into a new release, the testing process alone is substantial.
I'm sorry that this issue is in Fusion and I thank you for your patience as we find a fix. Hopefully in the meantime you can get the bulk of your orbits done with Free Orbit.
Lucas Prokopiak
Fusion 360 Product Manager (Sketch/Model)