SORMAS-Project icon indicating copy to clipboard operation
SORMAS-Project copied to clipboard

Case Creation - Possible to unselect case classification leading to error on save

Open raulbob opened this issue 8 months ago • 1 comments

Bug Description

In the new case dialog window it is possible to click twice on a case classification button causing none to be selected. Afterwards clicking save produces an error.

Reproduction Steps

  1. Use the "NEW CASE" button
  2. Complete the form.
  3. Click twice on "NOT YET CLASSIFIED" (the option should become un-selected)
  4. Click "SAVE"
  5. Error screen is shown with "Unexpected Errror"

Expected Behavior

  1. On save the "NOT YET CLASSIFIED" should be automatically selected if no other case classifications are on.
  2. Do not allow case classification widget to have no option selected.

Affected Area(s)

Web app

SORMAS Version

1.102

Android version/Browser

any

User Role(s)

National User

Server URL

qa.sormas.dev

Additional Information

No response

raulbob avatar Jun 17 '25 00:06 raulbob

@raulbob which disease was this for? we cannot replicate, we didnt get an error

SORMAS-EmelineJanigan avatar Jun 17 '25 16:06 SORMAS-EmelineJanigan

Normally on any disease, just make sure you complete the form and before saving click the enabled classification again and it will become unselected.

Fill in the form and uncheck the classification : Image

Save and you get an error: Image

raulbob avatar Jun 19 '25 16:06 raulbob

@SORMAS-JanBoehme are you able to replicate? i am not

SORMAS-EmelineJanigan avatar Jun 19 '25 18:06 SORMAS-EmelineJanigan

@raulbob I can not replicate it completely.

I can get the form to not have any case classification selected but it saves just fine and the case that is created is then set to "Not yet classified".

What does the log say when you get the error?

SORMAS-JanBoehme avatar Jun 20 '25 10:06 SORMAS-JanBoehme

Tried again to replicate without success. New case saved just fine, even with nothing selected for "Case Classification". The resulting case was set to "Not yet clasisfied" correctly.

Closing this issue.

SORMAS-JanBoehme avatar Sep 25 '25 12:09 SORMAS-JanBoehme