Configuring Rollup Automation Rules
The project creator or a role with the automation configuration permission can enable and disable automation rules to implement automatic status transition, workload statistics, story point statistics, and status synchronization. Once a rule is enabled, all work items and users in the project can trigger the rule.
| Rule Name | Description |
|---|---|
| Status Convolution | Synchronizes parent and child work items. For example, if all child work items are completed, the parent work item is automatically completed. For details, see Adding an Automation Rule for Status Rollup. |
| Labor hours Convolution-multiple issue types | Applies to workload rollup in all scenarios, including custom association scenarios. For details, see Adding an Automation Rule for Workload Rollup (Multiple Work Item Types). |
| Story Points Convolution-multiple issue types | Applies to story point rollup in all scenarios, including custom association scenarios. For details, see Adding an Automation Rule for Story Point Rollup (Multiple Work Item Types). |
| Labor hours Convolution | Applies to workload rollup in parent-child/upstream-downstream scenarios, excluding custom association scenarios. For details, see Adding an Automation Rule for Workload Rollup. |
| Story Points Convolution | Applies to story point rollup in parent-child/upstream-downstream scenarios, excluding custom association scenarios. For details, see Adding an Automation Rule for Story Point Rollup. |
Prerequisites
You have the automation permission on the work configuration page in the project.
Constraints
- If all child work items of the parent item meet the configuration in the rule condition and the target status of the parent item is the status that supports transition, the rule is executed.
- If the parent item has any child work items that do not meet the rule condition, when the rule is triggered, a record indicating no operation performed is generated and the parent item status is not transitioned.
- If there is no parent item, when the rule is triggered, a record indicating that no operation is performed is generated.
- If the parent item transition status configured in the rule does not support transition, when the rule is triggered, a record indicating an execution error is generated and the parent item status is not transitioned.
Adding an Automation Rule for Status Rollup
- Access the CodeArts Req homepage.
- Access a project and choose . The Automation page is displayed.
- Select the Automation Rules tab and click Create Rule.
- In the displayed dialog box, select Status Convolution.
- Click OK. The Status transfer: Status Convolution dialog box is displayed.

- Set an automation rule.
- Hover over Status transfer: Status Convolution and click
to set the name of the automation rule. - Select Trigger, Condition, and Action from the drop-down lists. The following figure is an example.

- Click OK. Check the new automation rule in the Automation Rules list. By default, the rule is enabled.

- Verify the automation rule by accessing the work item list again. For example, if you change the status of all child work items and collaborative downstream work items under the SG to Completed, the status of the SG is automatically updated to Completed. In addition, an automation rule operation history record is added to the History tab of the SG work item details page.
- Hover over Status transfer: Status Convolution and click
- When auto rollup is triggered, the corresponding rule is recorded on the Logs page. Click
in the Operation column to expand the log details. 
Adding an Automation Rule for Workload Rollup (Multiple Work Item Types)
Applies to workload rollup in all scenarios, including custom association scenarios.
- Access the CodeArts Req homepage.
- Access a project and choose . The Automation page is displayed.
- Select the Automation Rules tab and click Create Rule.
- In the displayed dialog box, select Labor hours Convolution-multiple issue types.
- Click OK. The Status transfer: Labor hours Convolution-multiple issue types dialog box is displayed.

- Set an automation rule.
- Hover over Status transfer: Labor hours Convolution-multiple issue types and click
to set the name of the automatic workload rollup rule. - Select Trigger and Action from the drop-down lists. You can set automatic rollup rules for the workload changes of multiple child work items at the same time. The following is an example of the configured workload rollup rule.

- Click OK. Check the new automation rule in the Automation Rules list. By default, the rule is enabled.

- Verify the automation rule by accessing the work item list again. For example, if you modify the planned workloads of any child work item (FSR), the workloads of its parent work item (SG) will be automatically updated to the sum of the planned workloads of all child work items, collaborative downstream work items, and associated snapshots under that SR. And an automation rule operation record is added to the History tab page.

- Hover over Status transfer: Labor hours Convolution-multiple issue types and click
- When auto rollup is triggered, the corresponding rule is recorded on the Logs page. Click
in the Operation column to expand the log details. 
Adding an Automation Rule for Story Point Rollup (Multiple Work Item Types)
Applies to story point rollup in all scenarios, including custom association scenarios.
You need to add the Story Point field for the work item types used in the project on the Field tab of the Work Item Fields and Workflow page. Only after the field is added can it be used in the corresponding work item. For details about how to add a field, see Adding a Field to a Work Item Type.
- Access the CodeArts Req homepage.
- Access a project and choose . The Automation page is displayed.
- Select the Automation Rules tab and click Create Rule.
- In the displayed dialog box, select Story Points Convolution-multiple issue types.
- Click OK. The Status transfer: Story Points Convolution-multiple issue types dialog box is displayed.

- Set an automation rule.
- Hover over Status transfer: Story Points Convolution-multiple issue types and click
to set the name of the automatic story point rollup rule. - Select Trigger and Action from the drop-down lists. You can set automatic rollup rules for the story point changes of multiple child work items at the same time. The following is an example of the configured story point rollup rule.

- Click OK. Check the new automation rule in the Automation Rules list. By default, the rule is enabled.

- Verify the automation rule by accessing the work item list again. For example, if you change the story points of any child work item (FSR), the story points of its parent work item (SG) are automatically updated to the sum of the story points of all child work items and collaborative downstream work items of that SG. And an automation rule operation record is added to the History tab page.
For story points of work item types (such as SG and FSR), you need to add the field to these work item types on the Work Item Fields and Workflow page. For details, see Adding a Field to a Work Item Type.

- Hover over Status transfer: Story Points Convolution-multiple issue types and click
- When auto rollup is triggered, the corresponding rule is recorded on the Logs page. Click
in the Operation column to expand the log details. 
Adding an Automation Rule for Workload Rollup
Applies to workload rollup in parent-child/upstream-downstream scenarios, excluding custom association scenarios.
- Access the CodeArts Req homepage.
- Access a project and choose . The Automation page is displayed.
- Select the Automation Rules tab and click Create Rule.
- In the displayed dialog box, select Labor hours Convolution.
- Click OK. The Status transfer: Labor hours Convolution dialog box is displayed.

- Set an automation rule.
- Hover over Status transfer: Labor hours Convolution and click
to set the name of the automatic workload rollup rule. - Select Trigger, Action, Equal, and Add from the drop-down lists. The following figure is an example.

- Click OK. Check the new automation rule in the Automation Rules list. By default, the rule is enabled.

- Verify the automation rule by accessing the work item list again. For example, if you modify the planned workloads of any FSR under an SG, the planned workloads of the SG will be automatically updated to the sum of the workloads of all its child work items and collaborative downstream work items. And an automation rule operation record is added to the History tab page.

- Hover over Status transfer: Labor hours Convolution and click
- When auto rollup is triggered, the corresponding rule is recorded on the Logs page. Click
in the Operation column to expand the log details. 
Adding an Automation Rule for Story Point Rollup
Applies to story point rollup in parent-child/upstream-downstream scenarios, excluding custom association scenarios.
You need to add the Story Point field for the work item types used in the project on the Field tab of the Work Item Fields and Workflow page. Only after the field is added can it be used in the corresponding work item. For details about how to add a field, see Adding a Field to a Work Item Type.
- Access the CodeArts Req homepage.
- Access a project and choose . The Automation page is displayed.
- Select the Automation Rules tab and click Create Rule.
- In the Work Item Status Transition Rule Template dialog box, select Story Points Convolution.
- Click OK. The Status transfer: Story Points Convolution dialog box is displayed.

- Set an automation rule.
- Hover over Status transfer: Story Points Convolution and click
to set the name of the automatic story point rollup rule. - Select Trigger, Action, Equal, and Add from the drop-down lists. The following is an example of the configured automation rule for story point rollup.

- Click OK. Check the new automation rule in the Automation Rules list. By default, the rule is enabled.

- Verify the automation rule by accessing the work item list again. For example, if you change the story points of any TSR under the FSR, the story points of the FSR are automatically updated to the sum of the story points of all child work items and collaborative downstream work items of the SG. And an automation rule operation record is added to the History tab page.

- Hover over Status transfer: Story Points Convolution and click
- When auto rollup is triggered, the corresponding rule is recorded on the Logs page. Click
in the Operation column to expand the log details. 
Related Operations
| Operation | Description |
|---|---|
| Add downstream collaboration status transition rule | Click the down arrow button next to Create Rule, and click Collaborate downstream status transfer in the drop-down list. The Work Item Status Transition Rule Template window is displayed. Repeat steps 3–7. |
| Edit rule name | Move the cursor over the rule name and click |
| Edit rule | Click |
| Copy rule | Click |
| Delete rule | Click |
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot



