Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LUX] RSV disease parse sample "Specify other type" field incorrect filled #13220

Open
sergiupacurariu opened this issue Dec 20, 2024 · 1 comment
Assignees
Labels
bug An error or misbehavior of an existing feature (ticket type) qa-verified Issue has been tested and verified by QA

Comments

@sergiupacurariu
Copy link
Contributor

Bug Description

In case the RSV-4 is present in the esante message the parsing will result in filling the field "Specify other type" with what is present in tag.

Reproduction Steps

  1. create an RSV disease xml message and add "RSV-4" in the message body
    2.push the message to Sormas
    3.create a case from the message
  2. go to case's sample
  3. check the field "Specify other type". This field will be filled with incorrect data from RSV-4
    ...

Expected Behavior

The field should be filled according to RSV-2

Affected Area(s)

Web app

SORMAS Version

1.100.0

Android version/Browser

Chrome

User Role(s)

National user

Server URL

No response

Additional Information

No response

@sergiupacurariu sergiupacurariu added the bug An error or misbehavior of an existing feature (ticket type) label Dec 20, 2024
@leventegal-she leventegal-she self-assigned this Jan 9, 2025
@markusmann-vg markusmann-vg added this to the Sprint 4 - SORMAS 1.101 milestone Jan 13, 2025
@richardbartha
Copy link
Contributor

@richardbartha richardbartha added the qa-verified Issue has been tested and verified by QA label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An error or misbehavior of an existing feature (ticket type) qa-verified Issue has been tested and verified by QA
Projects
None yet
Development

No branches or pull requests

4 participants