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.
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.
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