This document describes requirements in Scrum agile management.
CODING Project Collaboration provides two issue types: user storiesand requirements. You 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.
The user story is the smallest unit of work in the agile framework. It describes the value brought by software to users and is an important measure for agile requirements. Therefore, User story is enabled by default. To enable requirements, go to Project Settings > Project Collaboration > Issue Types and click Add Issue Type in the upper-right corner. Then, select Requirement and click Add.
In the following section, we will use a user story as an example to demonstrate how to manage requirements.
Sub-issues are specific activities carried out to fulfill requirements (user story or requirement). You can break down and assign requirements by creating sub-issues under them.
You can also select Create and click Full Create in the dropdown menu (keyboard shortcut: Shift + Enter) and enter details before creating a sub-issue.
3. After you have created the sub-issue, you can view it on the user story details page. You can also view the sub-issue in the requirement list.
4. On the user story details page, you can select
··· to the right of a sub-issue and click Change Parent Issue or Delete in the menu.
A requirement can be associated with multiple bugs in a project, but a bug can only be associated with one ** requirement**. For more information, see Manage Bugs.
···to the right of an associated bug and click Disassociate in the menu.
A requirement can be associated with existing test cases. On the user story 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. For more information, see Test Cases.
In the Description or Comments on the user story 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
# + reference ID/title of the issue to the commit information (for example, this is a commit #3). For more information, see Reference Resources and Upload Attachments.
The status of a requirement is the stage in the requirement's lifecycle and is used to organize and track the requirement.
The requirement list is the major workspace for relevant product personnel. You can switch between *Tree View, Tile View, and Kanban View to suit your needs. This helps you create a global view of all requirements and their progress in the current project. The next time you go to this page, the system will display the last used view by default.
When there are many requirements, flexibly use the search box and filters to quickly locate the information you need. For more information, see Manage Issue Views.
All changes to 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 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 import or export user stories and requirements. For more information, see Import and Export Issues.
On the user story 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 of the user story, if any, will be deleted. Proceed with caution.
If you simply need to delete a sub-issue, on the user story details page or details page of the sub-issue, select
··· and click Delete in the menu.