Issues

This video below shows how to manage Issues as part of a closed loop review in the native design application such as Microstation. The dialog shows a really useful searchable menu, but the reality is that this functionality has been removed and no...

Currently, permissions and access rights for a form are set by state. In a state a role can either have: no access view access edit access We would like to have more granular access rights on property level for each Status: Only role 1 can only ed...

We would like the ability to mass transition issues from the table view. Currently, if an assignee has 10+ issues that need to be transitioned to the next workflow, they have to open each one individually. Using the transitions from the table view...

the iTwin Owner needs to be able to delete comments (issues and tasks) within the iTwins especially if they get made incorrectly.

It would be nice to receive a summarizing mail with all issues, just like Microsoft Teams do with missed activities. This to avoid a spam of mails, when people are doing the design review. Therefore it could be nice to have the option to chose the...

It is currently possible to set an approver to a form status transition. It is even possible to do a conditional approval. We would like to add an automated approval or rejection after a number of days. This is to do with (German) hierarchies that...

When creating an issue in the PDF view/review tools, it would be nice if the dialog could be docked to the left or right of the view. Currently this dialog is a free floating entity and depending on view resolution can get stuck off screen when ch...

Is there a hidden binder that can be populated in a control which indicates what imodel an issue was created? In the dashboard/form views there are indicators that an issue came from an imodel or has a map location. It would be extremely helpful i...

In form workflow there are multiple valid options. Only 1 option is shown in full size then the others available are small when clicking the dropdown arrow. Users sometimes see these are not primary valid options due to the way they are presented....

in forms, each transition button can have a conditions that has to be met to use it. If a user selects the option then they get an error message that may not be intuitive. Can only transition buttons show up where the condition is met, or a button...