Emmanuel
My feedback
7 results found
-
3 votes
An error occurred while saving the comment An error occurred while saving the comment Emmanuel commentedGreat !
This would need to precise what kind of model to use for those subs -
12 votes
An error occurred while saving the comment Emmanuel commentedIf 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")"An error occurred while saving the comment Emmanuel commentedIt 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 monthIt 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)
Emmanuel supported this idea · -
6 votes
See our latest comment for more info.
An error occurred while saving the comment Emmanuel commentedIf 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...
-
1 voteEmmanuel shared this idea ·
-
4 votesEmmanuel shared this idea ·
-
25 votes
See our latest comment for more info
An error occurred while saving the comment Emmanuel commentedThink 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).
Emmanuel supported this idea · -
6 votesEmmanuel supported this idea ·Emmanuel shared this idea ·
And in which group (of which context) it must be created