REQUEST: Add More Schedule Options #77

Open
opened 2025-12-28 13:42:03 -05:00 by My-Random-Thoughts · 1 comment
My-Random-Thoughts commented 2025-12-28 13:42:03 -05:00 (Migrated from github.com)

I have a subscription that I pay every 2 years, and one every 10 years - both domain name renewals.
Having a number as well as the schedule name would be more powerful - but I realise it may be a lot harder for coding.

For example, you could then have

Schedule: [ 2 ] [ weeks ]
Schedule: [ 6 ] [ months ]

etc

Thanks

I have a subscription that I pay every 2 years, and one every 10 years - both domain name renewals. Having a number as well as the schedule name would be more powerful - but I realise it may be a lot harder for coding. For example, you could then have `Schedule: [ 2 ] [ weeks ]` `Schedule: [ 6 ] [ months ]` etc Thanks
bscott commented 2025-12-28 16:23:28 -05:00 (Migrated from github.com)

Thanks @My-Random-Thoughts -- Let me see what I can do, I understand the need for more complex schedules.

Thanks @My-Random-Thoughts -- Let me see what I can do, I understand the need for more complex schedules.
Sign in to join this conversation.
No labels
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
bscott/subtrackr#77
No description provided.