All ideas

Ability to move issue resolution flag after placed in iTwin design review. We currently have the ability to update the form details in the issues page itself, but the flag cannot be moved closer to the component after the issue has been created

Currently if you switch the tree view to “Categories” you see the same levels repeated for every model that uses it. Users wanting to control view by category don’t want to have to pick and manage multiple instances of the same level. When wanting...

Would like to be able to see the Manage Issues as graphics inside OpenRoads and OpenRail. As you can when you're looking at the issues inside the iModel.

Documents linked to the model (as attached in ORD, OBM, etc) should be visible in iTwin Design Review. Supporting documents are attached to the model so they are easily accessible to everyone and all information is available in one place. In Bentl...

The measurements that i have in the view i create with the issue are added to the issue but are very difficult to change or delete. I would like to be able to update a measure in the view, or add a new one or even delete one that was there.

The Design Review cross section tool provides for a Point Weight scale option - which works well. Similarly, could you provide a Line Weight scale option to assist making the lines more visible in the XS view?

We would like to be able to create a common IModel based on a group of already existing in iTwin iModel. (or connect iModels to a single container, similar to the existing REFERENCE FILE in OpenPlant or Microstation) For example, we plan to creat...

We used to integrate Iso Sheet information from an SQL database with Pipeline information. Would be nice to have a similar integration with PlantSight since 3D data is already available there.

Currently we have two sets of Drawing properties that don't talk to each other. Projectwise has Drawing Attributes but this is not pushed to properties in the Drawing that are configured to Schema attributes.

The current synchronisation of iModels prevents the individual naming of the 4 files that make up the cadastre documentation. It is necessary, for quality reasons, to avoid that several documents share the same name, so the current synchronisation...