Constraint can be triggered again while being verified
In case a constraint is being updated and we save the project the constraint verification is triggered again.
This is problematic for formal verification constraints.
Currently it is being caused by org.fortiss.af3.rcapplication.advisors.UpcomingObjectiveContributionItem.isConfigurationSatisfied as this function (I think) is called when saving a project.
But IMO we should update the constraint service to check a situation like this, i.e., to check if the constraint is being already verified before triggering it.
(from redmine: issue id 3329, created on 2018-03-08, closed on 2018-03-21)
- Relations:
- relates #3331