I love how cPanel handles this...

 

Their change logs give the tracking number and description of every change that is made in a way you can cross reference

 

This allows me to know when an item I submitted is formally addressed

 

Currently we have no formal way and have to hope an ST employee marks one of the possible many related posts as completed, etc

 

As ST is focused on using their tools the way these are handled will only get better as their products suite/tools get better and thats if they deem enriching them for bug reporting is worth it.

 

It's been mentioned they have an internal tool for tracking things but none of that sees the light of day.

Unfortunately when you block your customers from reporting bugs by putting up a community and claim it's peer to peer or require paid support to effectively communicate it just stifles your users from helping you make the product better.  Peer to peer communities are a total copout, sorry, it's your company, your products, read and respond.  Fortunately they do here from time to time so I do give them that credit.  But they should add staff to engage users in this community effectively and lift relevant cases to their internal bug tracker as they deem necessary.  In the end we suffer by this failed communication, look at the Mac Contacts app issue we've been enduring for years because NO ONE reported it!  Or we keep getting the nonsense about it's coming in vNext time after time!