iTwin Services Ideas

Hi, I attended training in iTwin model reviewing on the 20th May 2020, When we looked at how clash detection works, i realized that the integration into listing the clash as a "Issue" was done one by one, Clash management and transferring of clashes to the issues portal should be thought of as a bulk process, we can easy end up with a large number of clashes...1000s, in clash detection, we should have a very simple way of running through clashes, assigning them, rejecting them...ect and at the end be able to select only particular clashes"based on what or who we have assigned the clash to, and bulk import those clashes into the Issues portal. I would like to do weekly clash detection runs and bulk upload, this will give designer a weekly responsibility of clearing clashes and it will ensure that your clashes never get out of hand, on the reporting of issues....it would also be handy to be able to sort through issues based on if the issue was a clash, if the issue was picked up in a client review, if the issue comes from a internal review, this allows us to sort through issues, when sitting with a client, we dont always what them to see our internal issues but we must be able to filter and just show client specific issues. thanks