Dynamically populate fields for synced issues

[Dmitry Alabyan]

Greetings, Community!
I have two projects.
One - a work-management, with tasks serving as dossiers for campaigns we run.
Another - a kanban software board with tasks summing up the bills to be sent to the clients.
Current automation level: when a dossier is created and filled accordingly > manual trigger > creates a corresponding bill task in the kanban board. Carries over summary, custom fields, dates, numbers, etc.

My question would be - how to build an automation that would dynamically update bill tasks if any changes occured to the fields in the dossiers. 
Aka what would be the connector here across projects? Linking of the issues? any suggestions?

[Kalyan Sattaluri]

Hello @Dmitry Alabyan 

Please share how many of each are created usually.

Yes, At a high level, if your Billing Tasks (Project 2) are linked to Work Management Tasks (in project 1), then you could use Issue updated / field updated trigger & Branch logic next to update your Kanban board. But this linking needs to "many-many" , that is, if you have multiple work management tasks, each of them needs to be linked to all billing tasks stories. So it may get messy. 

Also, without knowing much, just suggesting an structure to organize if you havent already, You could have a Epic for each campaign. This can live in any project. Then you can have Work Management Tasks (in Project 1) and Billing Tasks (in Project 2) be under this Epic. You could do the same syncing here as well but it has added benefit of reporting etc.

Hope it helps.

[Dmitry Alabyan]

Indeed, this is what worries me. If, e.g. several issues will be linked to one
like, when we clone the initiall Work Management tasks since they're generic - the clone is also a link relationship..