When we create a template and then push the template out to a board.....and then make a change to the template. How do we push out the update to all of the boards?
@Lori Werner
update : I misread your question. I was answering based on template card not board.
As far as I am aware, and I did a quick test by adding a label on the template, it does not automatically update the created cards.
There is a {sourcecardname} variable in Butler for copied cards. This appears not the same as what is on the card point to the template:
"cardSource":{"id":"60d27a961d2ff17fdc5292e2","name":"A template",
I am imagining a 'helper' solution where you can have a checklist of all the created cards so that you can use it with Butler to automate the updating process. Or you can have a webhook on the template card such that it will detect a change, look for all the cards that was created and incorporate the change programmatically on each card.
The 'helper' solution is done. I will put it with an endpoint. It can be used with Butler to automate the changes to all card that was created from a template card. It can be used by developers via a http request.
It uses the "cardSource" taken from within the "copyCard" action.
This is a short video demonstrating the use of the above endpoint.
https://www.loom.com/share/ca15818b5a964538a2c07f16348712a9
a second video but using the same capability via a webhook or trigger that watches the template card
https://www.loom.com/share/a2633223634547f58284b98777b20e94
@Lori Werner the best way to resolve this sort of depends on what sorts of changes you want to synch. Do you want to simply make it so that when you create a new card in a list, the corresponding card is created in all lists on boards that have used this template? Or do you want to synch changes to existing cards? Basically you can do it, but you'd have to look at each scenario where you want to push your updates and write a specific automation for that.
@Iain Dooley
Agree. The automation will depend on the kind of updates. As the created cards would have undergone all kinds of activities and travelled across the board, the helper card allows you to have them collected based on sourceCard from the first copyCard action. Your post arise a good enhancement to add which is checklist by list names. That way the automation can be more targeted using the helper card.
We use Trello for tasks for our employees to follow. So let’s say we wanted to add an additional step that we wanted them to follow. We add that on the template and I don’t want to have to duplicate that 75 times on individual cards. I would rather just push out that update to all of the cards
Have you watched the videos? The helper card collects all the cards created from card template into a checklist just like you would with Butler collect card action. You can then literate through the checklist to update the 75 cards.
It uses the sourceCard info associated with the first copyCard action - aka when you used the template to create a new card.
The easiest workaround is to use hidden labels and you can collect all the cards with Butler. That assumes the label is not removed by your user.
It looks like you're new here. Sign in or register to get started.
