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

JCC appointment: Creating an appointment uses the wrong data, creating an appointment for a date in the past and an incorrect product #4103

Closed
alextreme opened this issue Apr 3, 2024 · 1 comment · Fixed by #4108
Closed

JCC appointment: Creating an appointment uses the wrong data, creating an appointment for a date in the past and an incorrect product #4103

alextreme opened this issue Apr 3, 2024 · 1 comment · Fixed by #4108
Assignees
@sergei-maertens
Labels
bug Something isn't working needs-backport Fix must be backported to stable release branch
Milestone
Release 2.6.2

Comments

@alextreme
Copy link
Contributor

Product versie / Product version

2.5.4

Omschrijf het probleem / Describe the bug

Taiga HadM #93

Creating an appointment via JCC uses the wrong data, this leads to an appointment for a date in the past and an incorrect product.

image

Stappen om te reproduceren / Steps to reproduce

No response

Verwacht gedrag / Expected behavior

No response

Screen resolution

None

Device

None

OS

None

Browser

No response
@alextreme alextreme added bug Something isn't working triage Issue needs to be validated. Remove this label if the issue considered valid. labels Apr 3, 2024
@sergei-maertens
Copy link
Member

I was suspecting timezone issues and looking at the hours, but note that this is about the year (2018).

@sergei-maertens sergei-maertens removed the triage Issue needs to be validated. Remove this label if the issue considered valid. label Apr 3, 2024
@sergei-maertens sergei-maertens added this to the Release 2.6.2 milestone Apr 3, 2024
@sergei-maertens sergei-maertens added the needs-backport Fix must be backported to stable release branch label Apr 3, 2024
sergei-maertens added a commit that referenced this issue Apr 3, 2024
@sergei-maertens
🐛 [#4103] Use the plugin appointment ID instead of our internal DB pk
db1de5e 
Appointment details were being retrieved using our internal database primary key,
but that looks up records from the appointment system that are unlikely to
match with the actual appointment ID recorded for a given appointment.
@sergei-maertens sergei-maertens mentioned this issue Apr 3, 2024
Merged
sergei-maertens added a commit that referenced this issue Apr 3, 2024
@sergei-maertens
🐛 [#4103] Use the plugin appointment ID instead of our internal DB pk
cba3d8c 
Appointment details were being retrieved using our internal database primary key,
but that looks up records from the appointment system that are unlikely to
match with the actual appointment ID recorded for a given appointment.

Backport-of: #4108
sergei-maertens added a commit that referenced this issue Apr 3, 2024
@sergei-maertens
🐛 [#4103] Use the plugin appointment ID instead of our internal DB pk
b37ebf1 
Appointment details were being retrieved using our internal database primary key,
but that looks up records from the appointment system that are unlikely to
match with the actual appointment ID recorded for a given appointment.

Backport-of: #4108
sergei-maertens added a commit that referenced this issue Apr 3, 2024
@sergei-maertens
🐛 [#4103] Use the plugin appointment ID instead of our internal DB pk
2eed48c 
Appointment details were being retrieved using our internal database primary key,
but that looks up records from the appointment system that are unlikely to
match with the actual appointment ID recorded for a given appointment.

Backport-of: #4108
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sergei-maertens sergei-maertens

Labels
bug Something isn't working needs-backport Fix must be backported to stable release branch
Projects
Development
Archived in project
Milestone
Release 2.6.2
Development

Successfully merging a pull request may close this issue.

Use the plugin appointment ID instead of our internal DB pk open-formulieren/open-forms
3 participants
@joeribekker @alextreme @sergei-maertens