I use a Kan Ban board style project as a master board for several teams. Some teams like to have their own board too.
We have tried to set up rules where moving a task in the source project (i.e. move to in progress, from “next”) “creates” that task in the appropriate section of the master board. The first time a task is dragged into one of these sections, the rule works (ex. moving from “next” to in progress on the source board, creates the task under “in progress” on the master board). However, when that task is moved to in-review on the source board - the task does not change sections on the master board (source board has a rule that if a task is moved to “in review” on this project, create that task under in-review on the master project).
If instead we use a custom field to trigger these rules, then it all works (ex. if status set to in review on source project, create this task under in-review on master project) - tasks would move around as expected.
One of two things could be done to make this experience better:
- make it so that the rules work? or
- make it so that a project can be filtered for tasks from a source project then status could managed all in one spot?