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.

Sign up for GitHub

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

Jump to bottom

Changing the outcome of the latest case from DECEASED to NO_OUTCOME doesn't set PresentCondition to UNKOWN #10496

Closed
ChristopherRiedel opened this issue Sep 30, 2022 · 0 comments · Fixed by #10497
Closed

Changing the outcome of the latest case from DECEASED to NO_OUTCOME doesn't set PresentCondition to UNKOWN #10496

ChristopherRiedel opened this issue Sep 30, 2022 · 0 comments · Fixed by #10497
Assignees
@ChristopherRiedel @AndyBakcsy-she
Labels
backend Affects the web backend bug An error or misbehavior of an existing feature (ticket type) major A functional requirement is incorrect or incomplete, ... (Severity for bugs/defects) persons qa-verified Issue has been tested and verified by QA
Milestone
Sprint 119 - 1.75.3

Comments

@ChristopherRiedel
Copy link
Contributor

ChristopherRiedel commented Sep 30, 2022 •
edited

Bug Description

Changing the outcome of the latest case from DECEASED to NO_OUTCOME doesn't set PresentCondition to UNKOWN but to ALIVE. This was defined in #525 and not changed accordingly in #2769.
This problem exists since version 1.50.0

Steps to Reproduce

Expected Behavior

Screenshots

System Details

  • Device:
  • SORMAS version:
  • Android version/Browser:
  • Server URL:
  • User Role:

Additional Information
@ChristopherRiedel ChristopherRiedel added bug An error or misbehavior of an existing feature (ticket type) backend Affects the web backend hotfix persons labels Sep 30, 2022
@ChristopherRiedel ChristopherRiedel added this to the Sprint 119 - 1.75.3 milestone Sep 30, 2022
@ChristopherRiedel ChristopherRiedel self-assigned this Sep 30, 2022
@ChristopherRiedel ChristopherRiedel changed the title Changing the outcome of the latest case to UNKNOWN doesn't set PersonCondition to UNKOWN Changing the outcome of the latest case to UNKNOWN doesn't set PresentCondition to UNKOWN Sep 30, 2022
ChristopherRiedel added a commit that referenced this issue Sep 30, 2022
@ChristopherRiedel
#10496: Set PresentCondition accordingly to UNKNOWN
8ecb600
@ChristopherRiedel ChristopherRiedel mentioned this issue Sep 30, 2022
Merged
ChristopherRiedel added a commit that referenced this issue Sep 30, 2022
@ChristopherRiedel
#10496: Set PresentCondition accordingly to UNKNOWN (#10497)
6874128
SORMAS Team 4 - TEC - Iteration Backlog automation moved this from Review to Testing Sep 30, 2022
ChristopherRiedel added a commit that referenced this issue Sep 30, 2022
@ChristopherRiedel
#10496: Change test accordingly
f45e4b7
MateStrysewske added a commit that referenced this issue Sep 30, 2022
@MateStrysewske
#10496 - Change unit test
80cb0bd
@StefanKock StefanKock added the major A functional requirement is incorrect or incomplete, ... (Severity for bugs/defects) label Sep 30, 2022
@AndyBakcsy-she AndyBakcsy-she self-assigned this Oct 3, 2022
@ChristopherRiedel ChristopherRiedel changed the title Changing the outcome of the latest case to UNKNOWN doesn't set PresentCondition to UNKOWN Changing the outcome of the latest case to NO_OUTCOME doesn't set PresentCondition to UNKOWN Oct 4, 2022
@ChristopherRiedel ChristopherRiedel changed the title Changing the outcome of the latest case to NO_OUTCOME doesn't set PresentCondition to UNKOWN Changing the outcome of the latest case from DECEASED to NO_OUTCOME doesn't set PresentCondition to UNKOWN Oct 4, 2022
@AndyBakcsy-she AndyBakcsy-she added the qa-verified Issue has been tested and verified by QA label Oct 4, 2022
@StefanKock StefanKock mentioned this issue Oct 5, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ChristopherRiedel ChristopherRiedel

@AndyBakcsy-she AndyBakcsy-she

Labels
backend Affects the web backend bug An error or misbehavior of an existing feature (ticket type) major A functional requirement is incorrect or incomplete, ... (Severity for bugs/defects) persons qa-verified Issue has been tested and verified by QA
Projects
None yet
Milestone
Sprint 119 - 1.75.3
Development

Successfully merging a pull request may close this issue.

Bugfix 10496 set present condition accordingly to unknown SORMAS-Foundation/SORMAS-Project
3 participants
@StefanKock @ChristopherRiedel @AndyBakcsy-she