-
Notifications
You must be signed in to change notification settings - Fork 144
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
[FRENCH TEAM] Handle follow-up visits when merging a case [1] #2652
Labels
Milestone
Comments
MartinWahnschaffe
added
change
A change of an existing feature (ticket type)
ch
Adaptations requested by or implemented for Switzerland
cases
labels
Aug 14, 2020
@markusmann-vg @xavier-calland is working on this in this sprint |
@MateStrysewskeSym This is the solution we decided today we merging, please comment it you prefer otherwise:
|
markusmann-vg
changed the title
Handle follow-up visits when merging a case
[FRENCH TEAM] Handle follow-up visits when merging a case
Aug 31, 2020
xavier-calland
added a commit
to GIP-GRADeS-BFC/SORMAS-Project
that referenced
this issue
Sep 1, 2020
xavier-calland
added a commit
to GIP-GRADeS-BFC/SORMAS-Project
that referenced
this issue
Sep 3, 2020
xavier-calland
added a commit
to GIP-GRADeS-BFC/SORMAS-Project
that referenced
this issue
Sep 3, 2020
xavier-calland
added a commit
to GIP-GRADeS-BFC/SORMAS-Project
that referenced
this issue
Sep 3, 2020
MateStrysewske
added a commit
that referenced
this issue
Sep 7, 2020
Issue #2652 - Handle follow-up visits when merging a case
MateStrysewske
changed the title
[FRENCH TEAM] Handle follow-up visits when merging a case
[FRENCH TEAM] Handle follow-up visits when merging a case [1]
Sep 8, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Description
#1886 has added follow-up visits to cases.
Problem Description
The process of merging cases has not been adjusted to this yet.
Proposed Change
Make sure that follow-up visits of a cases or correctly handled when merging them.
The text was updated successfully, but these errors were encountered: