hello,
it would be great to have the possibility to clone also the cards in the lists when cloning the board.
As we do monthly checks for our cars in the fire brigade we have the same tasks repeating any month.
i would cover the parts of the cars in cards like "car", "equipment" etc with md-based checklists as description.
Like this we could have templates for all cars that can be cloned at the beginning of each month. Or perhaps in an automated way automatically - as a next step :)
So, lists are already cloned, and i implemented the UI part for also cloning the cards.
@desperateCoder please see branch 608-clone-cards-when-cloning-boards, i left you a TODO in SyncManager#cloneBoard to respect the boolean flag cloneCards.
@skeal Thanks for your patience! I worked on this feature these days and have to admit, that it wasn't nearly as easy as i expected. I had several issues with concurrency and stuff, but I now finally have a kind-of "does what it should do" version:
APK download: 胁褦蠅伪褟褦, 喂 伪屑 茠伪畏垄褍!
As always: this is a Dev-version and safe to install besides your actual installation of the Deck app. Even if not anything might work perfectly yet, I can confirm it didn't "break" anything for me (no data loss or something).
Would you mind testing it, if everything works as expected?
I also had a hard time figuring out what actually happens with the assigned users. The app does everything right if you ask me, I saw all the calls, but somehow in my tests there were cases where a user was assigned to a card with originally no assignees... Would be very interesting, if this also happens to you.
Quick information what you get in this feature:
Would be great if you can tell us if this works for you like that and if you encounter any issues, especially regarding assigned users, thanks in advance!
CC: @stefan-niedermann
Ping @skeal :see_no_evil:
Sorry for not having answered yet. I tried it and it looked really good ... Until restart of your Deck Dev version. It then duplicated the copied cards again (Before: Fahrzeugcheck, Materialcheck; After: Fahrzeugcheck, Fahrzeugcheck, Materialcheck, Materialcheck)
This also is shown then in the browser version of deck in nextcloud.
So the board itself is copied once with cards and then the cards are duplicated again.
@skeal no worries, thanks for the reply!
Aaaw snap. I thought I had fixed that... On the other hand: the app is trying to make sure, the trucks are double-checked, its a feature! :smile: Just kidding, I'll see, if I can reproduce it or what else is wrong. Thanks for the feedback so far!
Your board has two lists, right? My first guess would be, that it is synced once per list...
Yes there are the lists "Zu erledigen" and "Erledigt" currently for testing. The board also has two cards in "Zu erledigen". "Erledigt" is empty currently.
@skeal Ok, so I investigated this a little more and couln't find any issues. I'd suspect a server-hickup or something. If you encounter any further issues, please report! This feature will be shipped with version 1.10.0. Enjoy (in case it works :sweat_smile:)
Most helpful comment
@skeal Thanks for your patience! I worked on this feature these days and have to admit, that it wasn't nearly as easy as i expected. I had several issues with concurrency and stuff, but I now finally have a kind-of "does what it should do" version:
APK download: 胁褦蠅伪褟褦, 喂 伪屑 茠伪畏垄褍!
As always: this is a Dev-version and safe to install besides your actual installation of the Deck app. Even if not anything might work perfectly yet, I can confirm it didn't "break" anything for me (no data loss or something).
Would you mind testing it, if everything works as expected?
I also had a hard time figuring out what actually happens with the assigned users. The app does everything right if you ask me, I saw all the calls, but somehow in my tests there were cases where a user was assigned to a card with originally no assignees... Would be very interesting, if this also happens to you.
Quick information what you get in this feature:
Would be great if you can tell us if this works for you like that and if you encounter any issues, especially regarding assigned users, thanks in advance!
CC: @stefan-niedermann