CONNECT Edition Known Issues?

Unfortunately Ryan, Bentley has a very different view than you and I regarding the publishing of "Known Issues" list. The subject had been raised quite a few times, accross different Bentley products, for example one of mine is below:

communities.bentley.com/.../110864

At the moment, what I'm doing is to do a search (using Bentley/Google search engine) for the mention of the words "defect"/"bug" and pick out the topics of interest and book mark them. Tedious, but that's all I've got to work with, until someone else share their wisdom for a better approach.

Another thing that I do is going through the "Resolved Issues" list of each new release. Sometimes that helps.

I get that from a business point of view, you wouldn't want to make the information about your product's issues readily available. However, we are not asking for anything that isn't publicly available. As I have said in my thread, I'm not interested in every Known Issues that Bentley and its users have identified, or the list of all Known Issues reported by users. What would be tremendously beneficial though would be able to see a list of Known Issues: reported by users AND accepted by Bentley as defects to be fixed for the next commercial releases.

I understands sometimes there are scenarios where custom solutions have be created for specific clients and only for those clients, I'm not interested in those.

"This issue have been reported in the past and defect (XXXXXXX) have been filed" - how many times that kind of response was given. Think of all the man hrs saved if there's a central place that we can go and match our issue with what have been filed.

Afterall, the information to create such list is already available in the public (albeit behind the wall of Bentley's forum) domain. We just need help from Bentley to give us the list they were able to make based on our feedback. Rather than having to spend time and effort to troubleshoot/report/identify/keep track the issues ourselves.

I get that from a business point of view, you wouldn't want to make the information about your product's issues readily available. However, we are not asking for anything that isn't publicly available. As I have said in my thread, I'm not interested in every Known Issues that Bentley and its users have identified, or the list of all Known Issues reported by users. What would be tremendously beneficial though would be able to see a list of Known Issues: reported by users AND accepted by Bentley as defects to be fixed for the next commercial releases.

I understands sometimes there are scenarios where custom solutions have be created for specific clients and only for those clients, I'm not interested in those.

"This issue have been reported in the past and defect (XXXXXXX) have been filed" - how many times that kind of response was given. Think of all the man hrs saved if there's a central place that we can go and match our issue with what have been filed.

Afterall, the information to create such list is already available in the public (albeit behind the wall of Bentley's forum) domain. We just need help from Bentley to give us the list they were able to make based on our feedback. Rather than having to spend time and effort to troubleshoot/report/identify/keep track the issues ourselves.

Let me re-phrase, or possibly change, the original question.
Where is a general forum or discussion group where folks who are migrating to Connect can find answers to common issues they have like finding commands, accomplishing work flow, etc. Simple things we can't find in the various help structure. For instance, how to I get access to text size while using edit text?
I searched and looked and read for a few days now and there is Nothing general, very frustrating. I'm finally migrating from v8i to Connect, it's going O.K., but little things are keeping me from getting back to full production.

I believe this is the place. Search the forum. If nothing is found place your question, if it's a bug, if your missing something, or maybe something else.

Regards.