defects

We probably wouldn't be able to supply you with a list of ALL defects filed for MicroStation CONNECT Edition that may be outstanding but you can request a list of those you or your company has raised. It may be best to contact the Bentley Account Manager or Sales Rep to obtain this list but you should be able to access all your Service Requests via the online manager.

Hi Andrew,

I have to day I am more and more disappointed with CE platform development (not only because of quailty, but because of approach). Bentley have mentioned several times they implemented agile style to software development, but it seems one from core features of agile - customer is integral part of development process - has been ignored.

It has been "best practice" implemented often today to integrate customers / users into the development process as much as possible. It requires bidirectional flexible and continuous communication through different channels. I know many projects (both commercial and open source) where list of know bugs is freely available because automatically published to web (and filtered when necessary because of e.g. internal or law reasons), also priorities for every sprint / release is available usually in blogs (or directly in bugs management pages), list of fixed bugs and known issues are automatically published for every release.

Bentley approach? Don't tell anything, hide every possible fact, be closed company as much as possible. It's expensive, when for every information an advice is "ask account manager or sales rep", both for Bentley and for customers.

With regards,

  Jan

Jan, 

A list of Resolved Issues has been supplied with every version of MicroStation CONNECT Edition released. This, of course, is filtered to those our development team and managers are happy to supply to a public post. For a list of all Defects and Enhancements much of this information would be company sensitive but any user wants to discuss what they have raised and to escalate anything they feel is important, we are always happy to discuss. This is where a discussion with the Bentley Account Manager is better organizationally rather than a public post to the Communities.

https://communities.bentley.com/products/microstation/w/microstation__wiki/27351/faq---microstation

Sorry, but you did not convince me.

Andrew Bell said:

A list of Resolved Issues has been supplied with every version of MicroStation CONNECT Edition released.

It pretty useless as it describes (and often with delay and not for all power products avaiable) only a fraction of changes implemented in a particular release.

Andrew Bell said:

For a list of all Defects and Enhancements much of this information would be company sensitive

False argument and explanation: In my opinion this discussion is not about private / sensitive information provided by customers, but about list of known defects that are typically "customers neutral".

Andrew Bell said:

This is where a discussion with the Bentley Account Manager is better organizationally.

Which is something completely different what I hear from my customers.

Regards,

  Jan

A list of defects (or at least defects not connected directly to software security) could actually be helpful to users.

I could see the benefit of being able to file a service ticket referencing a known issue so that it could be added to the list of people who need that issue to be resolved.

It could help users understand if there is something wrong with their process, or if the issue is an actual software bug.

It could be beneficial (or at least less frustrating) to see that, no, they haven't fixed this issue yet.

Jan Šlegr said:

Bentley approach? Don't tell anything, hide every possible fact, be closed company as much as possible. It's expensive,

I can only conclude Bentley is slow walking this dog on purpose, possibly to keep Select Service customers.

So the answer to my question, is NO

Hi Andrew,

A compromise would be a good position to start off with... 
1) As is, you list the defects that you are willing to share, and
2) You list all the defect numbers that are fixed.

The full list of defect numbers should not be a security issues, if there are no descriptions.  But that list allows those of us who have filed defects to see if that particular defect is supposed to be fixed.  That way, if I am waiting for defect #1234 to be fixed and it is not working, I know if I should be reporting the defect again (because it was supposed to have been fixed), or if I should be patient for the next release because it has not been addressed yet.

--Thanks,
--Robert

Hi Andrew,

A compromise would be a good position to start off with... 
1) As is, you list the defects that you are willing to share, and
2) You list all the defect numbers that are fixed.

The full list of defect numbers should not be a security issues, if there are no descriptions.  But that list allows those of us who have filed defects to see if that particular defect is supposed to be fixed.  That way, if I am waiting for defect #1234 to be fixed and it is not working, I know if I should be reporting the defect again (because it was supposed to have been fixed), or if I should be patient for the next release because it has not been addressed yet.

--Thanks,
--Robert

One way you could possibly list these if you have your defects raised through Service Requests is to list them in the online manager. I believe you may be able to perform an advanced search by the Status "Open - Defect Files" or "Open - Enhancement Filed".

https://apps.bentley.com/srmanager/MySRs

Otherwise you would probably need to discuss this with your Bentley Account Manager to get a list produced or if you feel any of these need to be Escalated.

Hi Andrew,

I have my list of defect numbers.  The thing is to compare that list to the list of "fixed" defects in the new release (when it is available.)

--Thanks,

--Robert