Microsoft
MicrosoftPablo_Lerner Thank you for sharing your list. With regard to the password issue, that's a difficult one to track down. Passwords for SSMS are stored in Windows Credential Manager. There is a limit to the number of credentials that can be stored, so there is a possibility that the limit is being reached. The next time a password doesn't appear when it's been saved, check Credential Manager to confirm the connection exists there.
For grouping objects by schema, we did implement that in ADS, but that is not something we have on the current roadmap for SSMS. That is a request we've seen from other users, so we are aware of it. I have heard other requests related to grouping Agent job and I know you entered a feedback item (Add organization to SQL Agent Jobs - Improve visualization of categories · Community (azure.com)), I would recommend encouraging others to vote for it so that we get a better idea of interest. I would suggest the same for your request related to IO and TIME stats, and for Service Broker, there are definitely folks that use it and find great value. We don't have a UX for it on our roadmap at this time. With regard to source control integration, this is something which exists in Azure Data Studio and we do not plan to bring it to SSMS. As you noted, there are third-party tools that fill this gap.
I recognize that these may not be the answers you want to hear; please understand that there are a myriad of improvements the community would like to see in SSMS. We use feedback items, upvotes, comments that explain why, and other channels to determine which improvements can provide the most benefit across as many users as possible.