In the Do This: section of automation creation, it would be great if it included a new rule where we could create a new Scheduled Ticket based on the
closure of the ticket the automation is running against.
Ideally, I'd create a rule that says when a ticket is closed, and the subject contains "X" phrase, schedule this ticket once in 100 days. The new scheduling rule could have a checkbox that allows for continual/repetitive scheduling if wanted, unchecked would be a one-off scheduled instance. The timescale could allow for minutes, hours, days, weeks, months, or years. However the Jitbit timescale feature set could allow.
I have scheduled tickets running every 100 days - password resets that are due to change every 120 days. If I'm late resetting the passwords by 5 or 10 days, then the next time the ticket is fired the reset is already short by 95 or 90 days. I'm still early in resetting the passwords, but I'm too early. It's less efficient. The effect stacks in each subsequent fire of the schedule and is exacerbated by how late to the ticket I am by my current workload.
In my case, upon closure of the ticket, in 100 days, a new ticket is opened matching the original's request. Rinse, repeat. How long I take to complete the ticket doesn't matter so long as I do it within the 20 days before the password reset is required. Now I can set an actual due date requirement that matters.