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

Jump to bottom

Hospital Informant: Create a case leads to an unexpected error #6062

Closed
VitaliHZI opened this issue Jul 5, 2021 · 2 comments
Closed

Hospital Informant: Create a case leads to an unexpected error #6062

VitaliHZI opened this issue Jul 5, 2021 · 2 comments
Assignees
@DavidBaldsiefen
Labels
bug An error or misbehavior of an existing feature (ticket type) cases major A functional requirement is incorrect or incomplete, ... (Severity for bugs/defects) qa-verified Issue has been tested and verified by QA vaadin-app Affects the Vaadin application
Milestone
Sprint 105 - 1.61.1

Comments

@VitaliHZI
Copy link

VitaliHZI commented Jul 5, 2021 •
edited

Bug Description

If you try to create a new case with a hospital informant, an expected error occured.

Steps to Reproduce

  1. Go to cases
  2. Click on "new case"

Expected Behavior

No error occurs.

Screenshots

image

System Details

Additional Information

image
@VitaliHZI VitaliHZI added bug An error or misbehavior of an existing feature (ticket type) major A functional requirement is incorrect or incomplete, ... (Severity for bugs/defects) labels Jul 5, 2021
@DavidBaldsiefen DavidBaldsiefen added this to Backlog in SORMAS Team 2 - DEV - Iteration Backlog via automation Jul 5, 2021
@DavidBaldsiefen DavidBaldsiefen self-assigned this Jul 5, 2021
@DavidBaldsiefen DavidBaldsiefen moved this from Backlog to In Progress in SORMAS Team 2 - DEV - Iteration Backlog Jul 5, 2021
DavidBaldsiefen added a commit that referenced this issue Jul 5, 2021
@DavidBaldsiefen
Fix NPEs when working on cases as hospitalinformant #6062
5959c1a
@DavidBaldsiefen
Copy link
Contributor

As discussed with @MartinWahnschaffe we will solve this problem (or followup problems) by automatically setting the case jurisdiction for hospital informants to the facility-jurisdiction, and disabling the fields so they can not be edited. Should this behavior be changed it should be part of a separate issue and not hotfix relevant.

@DavidBaldsiefen DavidBaldsiefen added this to the Sprint 105 - 1.61.1 milestone Jul 6, 2021
@StefanKock StefanKock added cases vaadin-app Affects the Vaadin application labels Jul 6, 2021
DavidBaldsiefen added a commit that referenced this issue Jul 6, 2021
@DavidBaldsiefen
Fix NPEs when creating case as HospInfo #6062
bef3360
@DavidBaldsiefen DavidBaldsiefen mentioned this issue Jul 6, 2021
Merged
@DavidBaldsiefen DavidBaldsiefen moved this from In Progress to Review in SORMAS Team 2 - DEV - Iteration Backlog Jul 6, 2021
DavidBaldsiefen added a commit that referenced this issue Jul 6, 2021
@DavidBaldsiefen
Move if-then-return to beginning of updateFacility #6062
f0d9348
DavidBaldsiefen added a commit that referenced this issue Jul 6, 2021
@DavidBaldsiefen
Merge pull request #6072 from hzi-braunschweig/bugfix-6062-hotfix-hos…
3676aa6 
…pinfo-jurisdiction

#6062 Fix NPEs when creating case as Hospital Informant
@AndyBakcsy-she AndyBakcsy-she added the qa-verified Issue has been tested and verified by QA label Jul 13, 2021
@AndyBakcsy-she
Copy link

Validated ticket on the latest SORMAS Version: 1.61.1 deployed on https://release-international.sormas.netzlink.com/
using Hospital informant user: TestUserInt1 / 8WawGQZwz5fG

BarnaBartha added a commit that referenced this issue Dec 15, 2021
@BarnaBartha
#6062 - add feature type property to add soft/warning validation for …
7620c0c 
…follow up until field
MateStrysewske added a commit that referenced this issue Dec 17, 2021
@BarnaBartha @MateStrysewske
#6062 - add feature type property to add soft/warning validation for … (
967f4f0 
#7526)

* #6062 - add feature type property to add soft/warning validation for follow up until field

* #6862 - Don't automatically overwrite follow-up until date when new property is enabled

* #6862 - Fixed merge conflicts

Co-authored-by: Maté Strysewske <mate.strysewske@vitagroup.ag>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DavidBaldsiefen DavidBaldsiefen

Labels
bug An error or misbehavior of an existing feature (ticket type) cases major A functional requirement is incorrect or incomplete, ... (Severity for bugs/defects) qa-verified Issue has been tested and verified by QA vaadin-app Affects the Vaadin application
Projects
None yet
Milestone
Sprint 105 - 1.61.1
Development

No branches or pull requests
4 participants
@DavidBaldsiefen @StefanKock @AndyBakcsy-she @VitaliHZI