iTwin Services Ideas

Got an idea? Share it with us. See an idea you agree with? Vote and join the discussion. Want to be more involved? Please sign up for Usability Testing.

Issue - model version lock

The Issue tool is used to capture design issues, but the Issue is not assigned to a version of the imodel. This means that the issue is visible in an earlier version of the model even if the model elements don't exist.


This could be solved if the Issue could be locked to the current model version. This could be enabled during Form creation.


An additional column in the Issue Dashboard could expose the model version that the issue was raised against. This would help during IDC design reviews to ensure issues were raised against the correct model version.

  • Jason Symonds
  • Nov 21 2022
Design review
  • Luc Poulin commented
    August 31, 2023 13:23

    In our case we would like as well the to have an option to explicitly display issues that does not belong to another version and that are not close.


    We want to make sure that we do not left behind issue not being resolve, especially for those who have the iModel as their primary interface.


    This way we could display issues not resolve from previous version or a more recent version.


    If we go further, each issue has a expected date or milse stone to me revolve, we can ask the iModel to display issue based on that criteria.

    Exemple:

    • Show me issue to be resolve at 70%

    • Show me issue to be resolve in the next month

    • etc.....

    Ultimately, a bottom panel with tab could display some analytic, like:

    A timeline showing the number of issue to be to be resolve per date

    A timeline of issue having been raised in the last month

    ×

    Attachments Open full size

  • Ian Joyce commented
    January 05, 2023 10:36

    I have added an image that details this idea

    I-734.jpg
    ×

    Attachments Open full size

Related ideas