After #1118 is merged, changing a plan's constraint version should update the constraint status to "unchecked". This was not included in #1118 because it wasn't scoped in initially; and after discovering that it was needed, it didn't seem like enough of a blocker to delay the original PR.
The current behavior is that when a user changes the selected version of a constraint in a plan, the nav bar and the constraints panel does not reflect that the constraints have not been completely checked. The current "workaround" is that the user would just have to remember to click the "Check constraints" button after changing any constraint version.
After #1118 is merged, changing a plan's constraint version should update the constraint status to "unchecked". This was not included in #1118 because it wasn't scoped in initially; and after discovering that it was needed, it didn't seem like enough of a blocker to delay the original PR.
The current behavior is that when a user changes the selected version of a constraint in a plan, the nav bar and the constraints panel does not reflect that the constraints have not been completely checked. The current "workaround" is that the user would just have to remember to click the "Check constraints" button after changing any constraint version.