Updated on 2025-08-25 GMT+08:00

Creating R&D Requirements

R&D requirements are delivered in project release plans and sprints. These requirements can be associated with raw requirements and system features.

Prerequisites

An IPD-standalone software project is available, in which you have permission to create and duplicate R&D requirements.

Procedure

  1. Access the CodeArts Req homepage.
  2. On the project homepage, choose R&D Requirements.
  3. Click IR. On the IR page, set related parameters.

    Table 1 Creating an IR

    Parameter

    Description

    Tag

    When creating or editing a work item, you can add a custom tag.

    Tag names can be marked in different colors.

    Title

    Title of a work item.

    Description

    Enter the background, value, and details of the R&D requirement based on actual conditions.

    Use text, images, or links.

    Attachment

    The maximum number of attachments for an R&D requirement is 100, and their total size cannot exceed 500 MB.

    Responsible Project

    Project that the R&D requirement belongs to. The value cannot be changed.

    Raised By

    Members who propose the requirement. Multiple proposers can be specified.

    Owner

    Member who is responsible for this requirement. Only one person can be specified.

    Priority

    Priority of an R&D requirement, including Low, Medium, and High. The default value is Medium.

    Release

    Release plan version of the R&D requirement.

    This parameter has a value only after the operations in Creating Release and Sprint Plans are completed.

    This parameter can be left empty. You can create a release plan and then associate it with the release plan.

    Sprint

    Next level of the release plan.

    This parameter has a value only after the operations in Creating Release and Sprint Plans are completed.

    The parameter value can be empty. You can create a sprint and then associate it with the sprint.

    Planned Start

    Planned start time of a requirement. The date format is yyyy-mm-dd.

    Planned Completion

    Planned completion time of a requirement. The date format is yyyy-mm-dd.

    The planned completion time cannot be earlier than the planned start time.

    Planned Workload

    Estimated workload from the planned start time to the planned completion time for this requirement.

    Domain

    Domain. The value includes software, hardware, software and hardware, functions, and performance.

    Breakdown Required

    Whether it is necessary to break down this requirement into smaller units.

    Reason for Non-Breakdown

    This parameter is displayed only when Breakdown Required is set to No.

    State the true conditions of the project.

    Copy To

    Project members to whom the IR is copied. After the copy is complete, the people selected for Copy To will receive a message.

  4. Click OK. The R&D requirement page is displayed, and "IR created." is displayed in the upper right corner.

    The new requirement is displayed in the R&D requirement list, and the requirement state is Initial.

    Figure 1 R&D requirement list

    After an R&D requirement is created, the people selected for Owner, Raised By, and Copy To will receive email and system message notifications. If not, set notifications or modify notification settings. For details, see Configuring Notifications.

Related Operations

You can perform the following operations on a new R&D requirement.

Table 2 Basic operations on an R&D requirement

Operation

Description

Modify title

Click next to an R&D requirement title to modify it.

Modify field

Click the target field value in the row of an R&D requirement to modify the value.

Create child requirement

Click in the Operation column of an R&D requirement to break it down into child requirements.

  • In the Break Down Subrequirements dialog box, click Add Subrequirement to create a child requirement. A maximum of 10 child requirements can be created at a time.
  • You can break down work items quickly. See Configuring Common Fields in a Project for related field configuration.

    If Quickly split sub-work items is enabled, the corresponding number of child work items are created based on the number of options selected. A maximum of 10 child work items can be created.

    If the work item already has child work items, the function of quickly breaking down work items does not work.

    If a work item is configured with multiple fields for quickly breaking down work items, the child work items are broken down based on the first field in the field template.

View association map

Click under in the Operation column of an R&D requirement to view all data of its associated items.

Duplicate R&D requirement

Click under in the Operation column. This process is the same as that of creating an R&D requirement.

Delete R&D requirement

Click under in the Operation column of an R&D requirement.
  • R&D requirements in change or baseline review cannot be deleted.
  • Once deleted, an R&D requirement is moved to the recycle bin. R&D requirements in the recycle bin can be restored or permanently deleted. After an R&D requirement is restored from the recycle bin, it restores to the original status.
  • Restoring a child requirement also restores its parent on the requirement path but does not restore its siblings under the parent.

Copy link

Click in the Operation column of an R&D requirement to copy its title, ID, current owner, status, and link to the clipboard.

Migrate R&D requirement

On the details page, choose > Migrate in the Operation column of an R&D requirement to migrate it to other projects.

  • R&D requirements that have been baselined, completed, or are currently under baseline review or change review cannot be migrated.
  • Batch migration is based on the selected top-level requirement type. IRs are migrated across projects and non-IRs within a project.
  • Requirements are migrated together with their child requirements.
  • After an R&D requirement is migrated to another project, the system automatically removes its tags, actual workloads, related items (except for collaborative requirements), and release plans, and only keeps the fields of the same type as the existing work items. The associated work items are automatically canceled.