And in which group (of which context) it must be created
This would need to precise what kind of model to use for those subs
If date attributes have had a default value, we could have used it with KQL function :
example : card is created with default date like "ahead("1 week")+period("1 month")"
It would make sense to define a duration that applies to the card created from the template :
if a recurring card is created monthly the 5th of the month, and the duration is set to 5 days, than each created cards would have a date from 5th to 10th of each month
It would also be very useful to define an offset and a duration for subcards (example : subtask 1 souhld be created 2 days after the start of the parent and should last 3 days)
See our latest comment for more info.
If implemented, perhaps it could be more handy for everyone to add an option on that automated task to create mirror card on another project in spite of moving it ? (Or doing two automated tasks)
Think it would ease a lot the work of some of us to have those mirror cards created automatically...
See our latest comment for more info
Think there's the same need for groups : it would be nice to configure either sub cards would be assigned to same groups when created or not grouped (like it is today).