[GH-ISSUE #3454] Offboarding Wizard - Incorrect date and time on Confirmation screen #1571

Closed
opened 2026-03-02 13:45:17 +03:00 by kerem · 2 comments
Owner

Originally created by @github-itsjefen on GitHub (Jan 24, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3454

Description

When using the Offboarding Wizard to schedule an offboarding, when I get to the Confirmation part the date is shown as a different date. See the attached screenshots, where the scheduled offboarding date is set as "01/24/2025 13:30" and the date and time in the Confirmation part is shown as "1/21/1970, 3:42:01 AM".

Image

Image

Note, the offboarding gets the correct date and time when the task is created. It's just in the Confirmation screen that it seems off.

Environment data

Non-sponsored instance: 
Front end version number: 7.0.5
Back end version number: 7.0.5
Tried Tenant Cache Clear: true
Tried Token Cache Clear: true
Originally created by @github-itsjefen on GitHub (Jan 24, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3454 ### Description When using the Offboarding Wizard to schedule an offboarding, when I get to the Confirmation part the date is shown as a different date. See the attached screenshots, where the scheduled offboarding date is set as "01/24/2025 13:30" and the date and time in the Confirmation part is shown as "1/21/1970, 3:42:01 AM". ![Image](https://github.com/user-attachments/assets/c78096ae-6a1e-4fb4-9af9-9f5594fd743d) ![Image](https://github.com/user-attachments/assets/213301bb-90f8-4767-936c-74cfc4ffce1f) Note, the offboarding gets the correct date and time when the task is created. It's just in the Confirmation screen that it seems off. ### Environment data ```PowerShell Non-sponsored instance: Front end version number: 7.0.5 Back end version number: 7.0.5 Tried Tenant Cache Clear: true Tried Token Cache Clear: true ```
kerem 2026-03-02 13:45:17 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 24, 2025):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug."

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

<!-- gh-comment-id:2612414824 --> @github-actions[bot] commented on GitHub (Jan 24, 2025): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/ If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug." Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
Author
Owner

@github-itsjefen commented on GitHub (Jan 24, 2025):

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

<!-- gh-comment-id:2612417989 --> @github-itsjefen commented on GitHub (Jan 24, 2025): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#1571
No description provided.