Hi there, glad to see this is on a long-term roadmap now! Just here to share my use case of the same need.
We have Brand, PM, and Design all who work together on the same projects. We sort of treat the Workspace as a database of each development item. Brand passes their project on to the PMs, who then manage all of the specs and dates. We move the item from Brand’s board to PM’s board to kick it off. This works decently for us.
However, where I run into issues is sharing relevant information with the Design team. When an item is created in the PM board, it is duplicated and certain columns are mirrored to the Design board. They really only need a few columns. Then, some columns from Design are mirrored back to the PM board (like when an artist is assigned). The Design team also has a lot of other columns that the PMs just don’t need, and they track their progress in a different way, which is why it is on a separate board.
Where we run into frustration/issue is when the item name has changed, when an item is deleted, or when an item is placed on hold. There is no good way to instantly communicate that except for myself to constantly maintain the boards and remember to keep an eye out for it.
The PM leaves recaps/updates in the PM board, which we wish we could share with Design so that they don’t have to leave their board to come find that information.
There are many other cases where it’s cleaner and easier to view a different board for tracking things for R&D. I have gone back and forth considering forcing everyone to join the same board and create ‘views’, but it is just not preferred. It would be an enormous, bloated board with hundreds of columns. Filters in a ‘view’ (at least in Pro level) are so easy to mess up, as well. I find the primary reason users prefer to use their own board is because they’re terrified of accidentally messing up something another team is working on.
When an item is complete, it doesn’t go away (since we produced it and it’s actively selling), so it moves to yet another board. Right now, when a change request comes up, I have to fetch the item from that board and migrate it back over to our active PM board. With better item connectivity, I could see a workflow in which it remains in our “Published” board but is connected to that active “PM” board for a change request. That way it wouldn’t temporarily look like that item isn’t in production.
Long story short, our whole workspace revolves around the same set of items but are used in different ways on different boards, and ‘Mirror columns’ just aren’t enough.
If there are ever Beta tests for this feature, I’d love to try it out!
Thank you for continuing to share your feedback around sharing or mirroring updates across connected items.