Updated on 2026-10-27 GMT+08:00

Procedure

RBAC

The service resources and system roles' default permissions vary depending on the project template (Scrum, Kanban, IPD-system device, IPD-standalone software, and IPD-self-operated software/cloud service).

In IPD-system device projects, CodeArts Req consists of the following service resources: Files, Recycle, Bug, Config, SF, SF Collection, IR, Plan Management, Review, RR, Task, Migration, and Collaboration. Each service resource has specific permission items.

Take the developer role of CodeArts Req as an example. If a developer needs the Break down requirements permission for IR work items, the developer needs to apply for the permission from the project manager. The project manager performs the following operations to assign the permission. The procedure for changing the permissions of other roles is the same.

  1. Assess the project, choose Settings > Permissions > Developer, and expand the CodeArts Req & Defect area. Figure 1 shows the default permissions of developers.

    Figure 1 Default developer permissions

  2. Click Edit on the top of the page, select Break down requirements of IR (as shown in Figure 2), and click Save. The developer permissions are configured successfully.

    Figure 2 "Break down requirements" permission configured for the developer role

  3. Developers check whether they can break down work items on the R&D Requirements page.

ABAC

This section takes an RR as an example. If members with the Config > Configure workflows permission want to control the field permissions of an RR in the Analyzing status, they can perform the following steps:

  1. Access the project and choose Settings > Work Item > Work Item Management > RR > Status Flow. The status list page is displayed.
  2. Click Edit. The status flow editing page is displayed.
  3. Click the Analyzing status node. The status information details page is displayed, as shown in the following figure.

    Figure 3 Status details page

  4. You can configure Role (not configured by default) to specify the roles that can edit certain fields based on your service scenario. Select roles for the field from the drop-down list, including temporary roles and project roles. Multiple roles can be selected. The selected roles are used to verify field editing permissions.

    • For operations in the Responsible Project: All selected roles take effect.
    • For operations in the Proposing Project: Only temporary roles take effect. Project roles are not included in the verification.

    In this example, the Role for Title and Description is set to Proposer. When an RR in the project is in the Analyzing state and the field edit constraint rule uses an OR relation, the current owner, users with the edit permission on RRs, and the Proposer can edit Title and Description. The settings are shown in the following figure.

    Figure 4 Setting roles for fields

  5. Click Update Status Flow and then OK. The configuration is successful, and the permission takes effect immediately.

Helpful Links