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
If case manager attempts to assign a benchmark to Para "A", then tries to assign the benchmark to Para "A" once more, the UI will allow them to (checkbox is empty next to name).
Furthermore, instead of showing an error, the app allows the case manager to actually create a duplicate task assigned to Para "A". This results in a duplicate row in the tasks table.
As of finishing #439 (backend solution), we now see this error which does prevent duplicate task creation.
EXPECTED
If case manager attempts to assign a benchmark to Para "A", then tries to assign the benchmark to Para "A" once more, the UI will show a checkbox next to their name b/c they are already assigned. The case manager can then choose to uncheck or recheck the checkbox to unassign or reassign.
Furthermore, if the front end UI checks are broken or bypassed, the app should not allow the case manager to actually create a duplicate task assigned to Para "A". Duplicate rows in the tasks table should not be created no matter what.
Notes:
In the beginning, the fetching of a benchmark should also fetch all paras assigned to said benchmark through tasks
Unassigning a para will delete a task
trial_data should be associated with a benchmark_id rather than a task_id
The text was updated successfully, but these errors were encountered:
ACTUAL
If case manager attempts to assign a benchmark to Para "A", then tries to assign the benchmark to Para "A" once more, the UI will allow them to (checkbox is empty next to name).
Furthermore, instead of showing an error, the app allows the case manager to actually create a duplicate task assigned to Para "A". This results in a duplicate row in the tasks table.As of finishing #439 (backend solution), we now see this error which does prevent duplicate task creation.
EXPECTED
If case manager attempts to assign a benchmark to Para "A", then tries to assign the benchmark to Para "A" once more, the UI will show a checkbox next to their name b/c they are already assigned. The case manager can then choose to uncheck or recheck the checkbox to unassign or reassign.
Furthermore, if the front end UI checks are broken or bypassed, the app should not allow the case manager to actually create a duplicate task assigned to Para "A". Duplicate rows in the tasks table should not be created no matter what.
Notes:
In the beginning, the fetching of a benchmark should also fetch all paras assigned to said benchmark through tasks
Unassigning a para will delete a task
trial_data should be associated with a benchmark_id rather than a task_id
The text was updated successfully, but these errors were encountered: