Skip to Main Content
iTwin Ideas Portal
Status Future consideration
Categories iModel management
Created by Guest
Created on Jun 8, 2018

adding comments to changesets

while its important to know what has changed in an iModel and who made the change, it is equally important to know the reason or why the change was made.  This way when we compare two versions in the future we can understand the context for the change.

  • Attach files
  • Guest
    Reply
    |
    Jun 11, 2018

    Good idea, and it would be better if we could track these against the Design Insights capabilities...

    Such as COST / SCHEDULE / SAFETY / PURPOSE ... ie was this change to meet a Design Requirement /  Change Notice etc