You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Okay, as mentioned in the meeting earlier today, allowing multiple people to be auto-assigned to a section breaks the integrity of the back-end and (in my opinion) creates more problems than it solves.
In fact, with this PR, being able to auto assign multiple people to the same review/stage/level will not be allowed.
Strongly suggest going back to the original behaviour where reviewers are simply "AVAILABLE" for assignment and have to self-assign themselves like they do everywhere else.
If anyone has a good reason why this shouldn't be like this, please explain it here. Cos allowing the database to exist in an inconsistent and problematic state (just look how many assignment bugs we cause!!) in order to save a user a couple of clicks is not worth it, so the argument for this will need to be pretty compelling.
Possible front end changes also required to remove button from un-assignment.
Un-assignment should not be available or visible.
Here the application is assigned to all users, yet admin is able to unassign
Admin unassigns and application fails
The text was updated successfully, but these errors were encountered: