I’m looking for what I believe is the same as @Joanna described and can give you a use case.
I work as in house CRO in a large company, we work with a centralised experimentation model, or in other words, we get ideas or things we need to AB test from the whole organisation for our central team to work on them (and they follow a process with different statuses like idea, research, prioritisation, planning, etc so the items have a quite long lifetime).
All our different teams are working in particular Monday boards with their own tasks on each, and that includes AB test tasks at different stages for say devs, designer, etc, but at the end of the day all the AB tests generated from different teams should be mirrored into a board where we can have a good overview on all new ideas for AB testing and their progress too. Otherwise we’d need to go through many boards filtering out items (AB tests) and updating them as we work with them, but always scattered.
We could agree with generating them from the same form and populating particular boards, but we need them in different boards, different groups and updated two-way as we update them anywhere (the update would happen from different team members in different teams working on their own board, and again, it is an item that contains around 15 fields and it gets many updates on them all throughout the item’s lifetime).