First off, thanks for providing a working plugin with a well thought UI.
Thank you for kind words. It is very rewarding to hear, that effect of my work is of any use for others. Actually the UI was my friend's idea, so I forwarded your words of appreciation :)
During my tests, I've noticed that your plugin creates just one new issue in the future when running renew_all. It would be great to have a field to create more than one future issue, for example 4 or 10.
To be strict: for recurrence schemes based on fixed schedule (i.e. those not depending on close time of last issue) the issues are created as long, as future issue reference date is before tomorrow and then one more future issue is created. If you run renew_all frequently enough it boils down to what you stated: there is always one future issue.
Our use case is simple: We need to track people's time in the office during these challenging Corona times. For that, it would be good if people could create recurrences for up to three months in our case so that others could plan their office stays too, because we are not allowed to have more that one person in a usual office room for example.
Given that you only care about recurrence schemes based on fixed schedule - that seems as a simple thing to do. I propose to add configuration setting which will tell at least how far into the future you want next issues to be created. For example: 0 days would yield the same behavior as now, and 1 month would create future issues up to 1 month from today and 1 additional issue after that . This way current logic would be maintained of always going one more recurrence further.
Regarding recurrence schemes based on closed date: they wouldn't be affected for obvious reasons.
Any comments/ideas regarding that?
Also this is the duplicate of #5, so I'm closing the old one.
Updated by 
Updated by 
Updated by