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
As a user of our web interface StatusDB,
I want the 'cancel samples' button and toggling the 'is_cancelled' field in the sample table to do the same thing,
So that I do not accidentally do something unintended.
Work impact
Answer the following questions:
Is there currently a workaround for this issue? If so, what is it?
NA
How much time would be saved by implementing this feature on a weekly basis?
NA
How many users are affected by this issue?
All production members cancelling samples
Are customers affected by this issue?
If issues happen
Acceptance Criteria
Criteria 1
Criteria 2
Criteria 3
...
Notes
The button "cancel samples" currently does a few things:
It toggles the is_cancelled values on the selected samples
It removes any CaseSample entries for the selected samples
It adds a comment to the samples stating who cancelled them
It deletes any cases which are not tied to any sample after their cancellation
Toggling the is_cancelled value in the table only does step 1, but seemingly should do the same. Otherwise we maybe should rename something so that they are not semantically identical but in reality quite different.
We should probably add a little popup with a tool tip describing what the buttons do as well.
The text was updated successfully, but these errors were encountered:
As a user of our web interface StatusDB,
I want the 'cancel samples' button and toggling the 'is_cancelled' field in the sample table to do the same thing,
So that I do not accidentally do something unintended.
Work impact
Answer the following questions:
Acceptance Criteria
...
Notes
The button "cancel samples" currently does a few things:
Toggling the is_cancelled value in the table only does step 1, but seemingly should do the same. Otherwise we maybe should rename something so that they are not semantically identical but in reality quite different.
We should probably add a little popup with a tool tip describing what the buttons do as well.
The text was updated successfully, but these errors were encountered: