One of the core practices in Kanban is to pull the cards from one column to another based on your capacity or the WIP limit defined for the individual column. But one needs to exercise caution in doing so, especially for the card that has multiple child cards and can only move from initiation to completion based on how its child cards get completed.

Many a time, in a development lifecycle, a parent card can move from stage A to stage B, when all the child cards about stage A get completed and archived. So, it is not only important that we automate this card movement so that one can save time and effort of manually moving the parent card while ensuring relevant child cards are Done but also enforce a rule that ensures the parent card does not move erroneously.

To achieve this purpose, we have an option to track the movement of cards using the portfolio lane that enables the card movement rule-driven and automated.

  • Was this helpful?
  • Yes   No