This document describes requirements in classic project management.
Open Project
1. Log in to the CODING Console and click Use Now to go to CODING page.
2. Click
in the upper-right corner to open the project list page and click a project icon to open the corresponding project.
3. In the menu on the left, click Project Collaboration.
A requirement refers to a software feature that users need in order to solve a certain problem or achieve a certain goal. In the Requirements module in CODING Classic Project Management, teams can quickly break down and assign development tasks. You can create requirements and break down larger ones into smaller sub-requirements. Also, tasks and bugs can be created for or associated with requirements.
1. Open any project and select Project Collaboration > Requirements. Click Create Requirement in the upper-right corner of the module and enter a requirement title, requirement description, and other basic information to create the requirement.
2. After you have created the requirement, you can set the assignee, plan the parent iteration, adjust the priority, and set the start date. Teams can customize the fields and dimensions of requirements to suit their management needs. See Custom Issue Fields for configuration details.
Sub-issues (sub-requirements and sub-tasks) are specific activities for achieving requirements. You can break down and assign requirements by creating sub-issues for a requirement.
A requirement can be broken down into sub-requirements, and a sub-requirement can be broken down further. A maximum of 5 levels of sub-requirements are supported. Take note that a requirement can have only one parent requirement at any one time.
1. On the requirement details page, select Break Down Requirement.
2. You can simply enter a title to quick create a sub-requirement. You can also select Create and click Full Create in the dropdown menu (keyboard shortcut: Shift + Enter) and enter details before creating a sub-requirement.
To associate an existing requirement, do a quick search by issue ID or title.
3. After you have created the sub-requirement successfully, you can view it on the details page of the parent requirement. You can also view the sub-requirement in the requirement list.
4. On the requirement details page, select ··· to the right of a sub-requirement and click Create Sub-Requirements in the menu.
Alternatively, on the details page of the sub-requirement, select Break Down Requirement at the top to create sub-requirements of the sub-requirement.
5. On the requirement details page, you can select ··· to the right of a sub-requirement and click Change Parent Requirement in the menu.You can also select Disassociate.
A requirement can be broken into sub-tasks. A task can only be associated with one parent requirement at any one time.
1. On the requirement details page, select Break Down Task.
2. You can simply enter a title to quick create a sub-task. You can also select Create and click Full Create in the dropdown menu (keyboard shortcut: Shift + Enter) and enter details before creating a sub-task. To associate an existing task, do a quick search by issue ID or title.
3. After you have created the sub-task successfully, you can view it on the details page of the parent requirement. You can also view the sub-task in the task list.
4. On the requirement details page, you can select ··· to the right of a sub-task and click Change Parent Requirement in the menu. You can also select Disassociate.
A requirement can be associated with multiple bugs in a project, but a bug can only be associated with one requirement.
1. On the requirement list page, select Associate Bug at the top and click Associate to Existing Bugs or quick create a new bug and associate it.
2. On the requirement details page, you can select ··· to the right of an associated bug and click Disassociate. You can also select Disassociate in the menu on the right of the bug details page.
You can view requirements that are currently associated and disassociate or switch between them.
3. On the bug details page, select ··· in the upper-right corner and click Convert to Requirement.
A requirement can be associated with an existing test case. On the requirement details page, select ··· at the top and click Associate to Test Case in the menu. Search for a test case by its ID or title and then associate it. See Test Cases for details on creating and managing test cases.
In a requirement, you can configure an existing issue as a pre-issue or post-issue with a block relationship. On the requirement details page, select ··· at the top and click Block Relationship in the menu. Search for an issue by its ID or title and then associate it. You can switch between pre-issues and post-issues. For more information, see Block Dependency.
In the Description or Comments on the requirement details page, you can use # + reference ID/title to select a resource. The resource referenced will be shown in the References list. If the current requirement has been referenced by another resource, the resource will be shown in the Referenced By list of the requirement.
You can also associate a code commit with an issue. When committing code, add the # + ID/title to reference of the issue to the commit information (for example, this is a commit #3). See Reference Resources and Upload Attachments for details.
The status of a requirement is the stage in the requirement's lifecycle and is used to organize and track the requirement. Requirement statuses include the following four by default: "Not started", "Under development", "Under testing", and "Completed".
1. After creating a requirement on the requirement list page, go to the requirement details page. The requirement status is Not started by default. Select options from the dropdown menu on the right to switch its status.
2. On the requirement list page, you can switch the status to the current stage of the requirement in the Status column.
3. Select Project Settings > Project Collaboration > Issue Types > Requirements, and then select Workflows to set custom requirement workflows. For more information, see Custom Workflows.
On the requirement list page, you can switch between *Tree View, Tile View, and Kanban View to suit your needs. This is the main working interface for product-related personnel and can help give you an overall idea of all requirements in the current project. When you return to this page, the system will show the last view used by default.
When there are many requirements, you can quickly view the content you need amid the sea of information by using the search bar or filters. For more information, see Manage Issue Views.
All changes in a requirement are recorded in the action log. On the details page, select ··· in the upper-right corner and click Earlier Versions in the menu to view all versions sorted by time. Version backtracking allows you to restore an earlier version. For more information, see Version Management.
You can batch import and export requirements. On the requirement list page, select ··· in the upper-right corner and click Import/Export Requirement in the menu. See Import and Export Issues for details.
On the requirement details page, you can select ··· in the upper-right corner and click Delete in the menu. This will not change the status of associated bugs, but all sub-issues (sub-requirements and sub-tasks) of the requirement, if any, will be deleted. Proceed with caution.
If you simply need to delete a sub-requirement, sub-task, or bug, on the requirement details page or details page of the sub-requirement, sub-task, or bug, select ··· and click Delete in the menu.
Yes
No
Was this page helpful?