Consider a parent card having many child cards linked to it. As a part of the development life cycle, the parent card needs to traverse through various stages before it gets completed. At every stage, there are a couple of child cards that need to be completed before the parent card moves from one stage to another. If we have to do it manually on the Kanban Board, it would be quite strenuous and error prone as we have to ensure all the child cards are archived at the right stage before we can move the parent card further towards the completion. To avoid such manual effort, we have introduced the auto movement of parent card, which lets the parent card automatically move from one column to another as its child cards are archived or moved to the Done column.
The Auto Movement is only available with SwiftKanban Enterprise License. Please make sure you have the Enterprise license if you wish to use this feature. If you are a SwiftKanban Team or Group License subscriber and would like to use the Auto Movement, you will need to upgrade to the SwiftKanban Enterprise License. For more information on the pricing, please refer to this page. To avail the Enterprise License, please contact us at email@example.com.
To use this feature, we must first enable the Enable auto Movement of Parent card policy on the Board policies page. Read more about the Board Policies here.
Let us consider a Kanban board having Welcome Page for Mobile App as a parent card and its six child cards:
- Requirement Gathering
The swim lane of the parent card includes columns that represent different stages of the workflow. In our example, the columns have similar names like child cards (Requirement Gathering, Wireframing, Design, Development, Testing, and Deployment). Moreover, each column is also divided into two sub-columns; In Progress and Done.
The child cards are placed under a separate swim lane which has three columns: To-Do, Doing and Done. Each child card is considered complete when they move to the Done column or been archived.
In our example, if the parent card is in Requirement Gathering#In Progress column of the Parent Card lane, then the child card “Requirement Gathering”, which is associated with the Requirement Gathering stage, should be archived or moved to the Done column in the Child Card lane before the parent card can move to the next Requirement Gathering#Done column.
Let us now understand how to automate this movement using this Auto-movement feature:
- Open the Bulk Edit page of the parent card (In our example, it is the Welcome Page for Mobile App) via the Linked Cards To know more about the Bulk Edit, read it here.
- In the Linked Cards tab, click Bulk Edit option on Side toolbar or click the Bulk Edit button in the upper right corner to set the Associated Parent Column for each child card.
For each child card, we need to set the Associated Parent Column, which means when that child card is archived or moved to the Done column, then, if the parent card is in the defined Associated Parent column, it will automatically move to the next column as set via the Board Editor.
In our example, for the auto movement of Welcome Page for Mobile App parent card, we need to select the Requirement Gathering child card in the Bulk Edit and set Requirement Gathering#In Progress as its Associated Parent Column.
Next, we navigate to the Kanban Board and set the desired next column of the Requirement Gathering#In Progress column via the Board editor.
Note: One must have the Admin or Manager role in the Board to access the Board Editor.
On the Board Editor, we open the column settings for the Requirement Gathering#In Progress column by double-clicking it and select the Requirement Gathering#Done for the Next Column field, which means the parent card, if in Requirement Gathering#In Progress column will automatically move to Requirement Gathering#Done provided the associated child cards are complete.
Similarly, we can define the Associated Parent column for all the child cards and then navigate to the column settings in the Board Editor to set the next column for all those Associated Parent columns. This will make sure that the parent card automatically moves from one column to another in a sequence defined by us as the child cards linked to the different stages of the parent lane get completed one after another.