mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #3274] JIT admins not being deleted after end time #1536
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1536
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rajeevan23 on GitHub (Jan 15, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3274
Originally assigned to: @kris6673 on GitHub.
Description
Hello
We have noticed that JIT admins are not being deleted after the end time. The scheduler shows the status as "Completed" but displays the following error message:
Thanks,
Raj
Environment data
@github-actions[bot] commented on GitHub (Jan 15, 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!".
@rajeevan23 commented on GitHub (Jan 15, 2025):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@mruiterHU commented on GitHub (Jan 15, 2025):
I second this
@kris6673 commented on GitHub (Jan 15, 2025):
I would like to work on this please!
@github-actions[bot] commented on GitHub (Jan 15, 2025):
Great! I assigned you (@kris6673) to the issue. Have fun working on it!
@kris6673 commented on GitHub (Jan 15, 2025):
Thanks the making the issue @rajeevan23! Has been fixed in dev and will be en next hotfix/release.
You will need to do the Expiration Action manually, for the JIT admins created until the fix is released.
@rajeevan23 commented on GitHub (Jan 15, 2025):
Thank you @kris6673 !
@kris6673 commented on GitHub (Jan 17, 2025):
Added in dev and is in yesterdays hotfix. You can close this as completed @rajeevan23 :)