Content:
1. How to create the rule?
2. How to set up and enable the rule?
3. Practical examples for using the 'Relative Card is Moved' rule?
This Business rule will automatically move a card to a specified position when its relative card is moved to a predefined position. A typical example would be to have two relative cards in different boards, so when the card on board A is moved to a given column/lane, then its relative in board B will be moved to the defined column/lane too.
1. How to create the rule?
Only users with "Account Owners" or "Manage Business Rules" privileges can create business rules.
Go to your Administration panel at the top right of your screen and open the Business Rules tab -> select the "Relative card is moved" rule.
Note: In case that there is a set of defined rules to your account -> use the Add new rule button at the upper right side of the panel.
2. How to set up and enable the rule?
The "Relative card is moved" configuration panel has the following fields and properties:
In the Name and Description fields, you can define the name of the rule and give a description of the scenario you will achieve with it. This way you can create an overview of your active business rules, as upon creation every automation is present in the Business rule panel.
PRO tip: You can specify the board name in the rule name in order to easily distinguish rules configured for each of your boards.
You can share the rule with other users (e.g. with a Workspace Manager of a board), if appropriate. In this case, they will be able to edit/disable/enable the rule.
The Business rules are a sort of "point-and-click" programming language with which you can automate any process.
Each Business rule has three main properties: When; And; Then.
1. WHEN - this is the event which will trigger an action when it occurs (i.e. a relative card is moved).
2. AND - here you define the filters, which specify the conditions under which the actions should be triggered.
- Position: the filter position is mandatory for this rule. There are two options: position is/is not - select one of the options from the dropdown. Click on Not Set to select a board from the dropdown and a position from the board minimap (you can select a cell or an entire column/swimlane by clicking on its name).
Click on "or" to add extra positions and optimize the scope of the rule. Use the minus sign to remove a position.
- Click on the Add new property button to add extra filters, if necessary. Select a Regular field or/and a Custom field -> click on Add.
-
For all time-related fields you can select the following units: Days, Hours, Minutes, Seconds. You can also set Custom Fields that you have created and added to the corresponding boards in your Workspaces as a filter.
When you have added the filter, set it up by clicking on Not set or enter a value.
Note: You can add as many filters as you wish by clicking on Add new property and repeating the steps.
3. THEN - Define the position where the relative card is to be moved.
Click on Add Action -> click on Choose where to move -> select the board and position from the board minimap (you can select a cell or an entire column/swimlane by clicking on its name).
In addition, for cases where you have more than 2 relative cards linked together, you can create a filter that specifies where to move each relative card separately. To define where multiple relative cards should be moved to, all you have to do is add a new action and then create a specific filter (e.g. board, workflow, swimlane etc) for it.
To enable the rule -> click on the green checkmark at the top right corner of the configuration panel.
Click on the red x-sign to cancel the creation of the rule. Read more about what are relative cards and how to create them.
3. Practical examples for using the 'Relative Card is Moved' rule?
This rule comes in handy when a lot of connected cards on the same level (relatives) are involved. One can use this rule to solve a lot of scenarios but the most common one is the cross-board moving of relatives. The rule goes as followed in a software development scenario:
- Whenever a card is moved to 'Done' (i.e. Developed) on the Development workflow, move the relative to the Ready to Start (i.e. Ready for testing) on the QA workflow.
This way these moves are automated and not forgotten and further improve the efficiency of the teams.
In addition, one can use this rule for multiple relatives scenario. Imagine a card with 3 relatives where only some of them need to move when a specific one is moved. For example with they are a part of the same project but belong in different swimlanes / are different types of work.
