Recurring ticket to be executed a fixed number of days after last ticket closed??

[DAVID VALENTE]

A built in account password expires every sixty days and needs to be changed.  After a recurring task is closed, I'd like the next iteration of the ticket to be created 50 days from that moment with a due date 10 days after creation.  We are using The Scheduler for recurring tickets.  Simply setting a time interval trigger will create a moving scale and after a few times executions the window will be way off.

[John Funk]

Hey David,

Why don't you just set a Due Date of every 60 days and warn them 10 days in advance to change it?

[DAVID VALENTE]

I don't see the option to set a warning.  I'd also prefer to not have the ticket created and sitting idle in open issues for 50 days.

[John Funk]

The warning would be in the email sent to them 10 days in advance. Also, what's the harm of them ticket sitting idle in the Backlog for 50 days if it automates your process and works?