Help Center/ CodeArts/ User Guide/ Preparations/ Managing Project Notifications/ Setting DingTalk Subscriptions
Updated on 2026-01-29 GMT+08:00
View PDF
Share

Setting DingTalk Subscriptions

Scenario

When any of the following events occurs, CodeArts sends a message through HTTP to the DingTalk group that has subscribed to the event.

Table 1 Event types

Category

Event types

Raw requirement

Create/Submit

Edit

Delete

Change

Update status

Ticket reminder added

Comment

System feature (SF)

Create

Edit

Delete

Change

Baseline/Unbaseline

Update status

Ticket reminder added

Comment

R&D requirement (IR/SR/AR)

Create

Edit

Delete

Change

Baseline/Unbaseline

Move

Comment

Ticket reminder added

Update status

Task

Create

Edit

Delete

Comment

Ticket reminder added

Update status

Bug

Create/Submit

Edit

Delete

Move

Update status

Ticket reminder added

Comment

Review

Submit

Transfer to others

Cancel/Reject

Change object reviewed

Change object decision-making completed

Review or decision-making completed

Delete

Comment
Table 2 Event types

Category

Event types

Repository

Capacity warning

Repo deleted

MR

MR opened

MR updated

MR merged

MR reviewed

MR approved

Review created

Review comment resolved
Table 3 Event types

Event Type

Notification Content

CodeArts Pipeline

Completed
  • Pipeline name
  • Pipeline execution description
  • Executor
  • Trigger
  • Project name
  • Execution time
  • Running status

Failed

Paused

Suspended

Ignored
Table 4 Event types

Event Type

Notification Content

Check task

Completed

  • All
  • Gate check passed
  • Gate check failed
  • Check result
  • Gate check result
  • Number of issues
  • Redirect URL
  • Executor
  • Completion time
Table 5 Event types

Event Type

Notification Content

Build task

Task successful
  • Task name
  • Executor
  • Execution time

Task failed

Task disabled

Task deleted

Task configurations updated
Table 6 Event types

Event types

Notification Content

Application

Application deployed
  • Application name
  • Execution result
  • Execution ID
  • Executor
  • Execution time
  • Project name

Deploy application failed

Deploy stopped

Constraints

  • This function is now available in the AP-Singapore region.
  • CodeArts Req configuration is only available for IPD projects.

Prerequisites

You have created a CodeArts project, and your role in the project is Project Administrator or Project Manager.

Procedure

  1. Go to the CodeArts homepage.

    1. Log in to the CodeArts console, click , and select a region where you have enabled CodeArts.
    2. Click Go to Workspace.

      If your account uses the old billing mode (see Old Billing Modes), click Access Service.

  2. Click the target project name to go to the project.
  3. In the navigation pane, choose Settings > General > Notifications.
  4. Click the DingTalk tab.
  5. Configure the parameters and click OK.

    Figure 1 Configuring DingTalk notifications (CodeArts Pipeline is used as an example.)
    Table 7 Setting DingTalk subscriptions

    Parameter

    Description

    URL

    The webhook URL of your DingTalk robot. Start with http:// or https://. The URL cannot exceed 256 characters.

    Event types

    Event types that can trigger a DingTalk notification. For details about the supported event types, see Scenario.

    Notification content

    Content of the DingTalk notification. For details about the configurable content, see Scenario.

    This parameter is optional. Configure it as needed.

    @user_id

    DingTalk user IDs of the members you want to mention. Separate the IDs with semicolons (;). The total IDs cannot exceed 1,000 characters. Digits, letters, semicolons (;), periods (.), hyphens (-), underscores (_), and at signs (@) are supported.

    This parameter is optional. Configure it as needed.

    @Mobile numbers

    Mobile numbers of the members you want to mention. Separate mobile numbers with semicolons (;). The total mobile numbers cannot exceed 1,000 characters. Digits and semicolons (;) are supported.

    Secret

    If your DingTalk robot has enabled signature-based encryption in security settings, enter the signing secret with a maximum of 2,000 characters.

    The updated configuration is displayed.

Parent Topic: Managing Project Notifications