Issue classification and definition _ visualization

Issue classification and definition: fine-grained splitting of product requirements into the project Department to achieve rapid development, validation and delivery goals.

Issue a total of 5 categories: Story/newfeather/task/sub_task/bug New Feather: Refers to the user needs, including functional requirements and non-functional requirements, it is directly reflect the user value, can be split into Story and Task. Story: is a product unit of value to the user, the minimum work package (function, performance, security, reliability, etc.) delivered to the customer. can be delivered independently (with other modules without reliance) small enough to be completed within three weeks (including analysis, design, development, testing) clear acceptance criteria (clear functional and non-functional acceptance criteria) clearly identify the risk (technical risk, etc.) task: Refers to technical tasks, such as technical pre-research, testing tasks, optimization program (performance), deployment environment, and so on. Sub-task: A lower-level task that is attached to story/task cannot exist alone. is a single story/task decomposition of the specific implementation of the focus of the smallest unit, is the support story/task implementation of the outside the youngest task, subtasks have no dependencies between. Bugs: A barrier or state that deviates from the requirements specification of a software/system, or hinders its expression from being consistent with the requirements specification of the software/system, can be functional or non-functional. Our requirements specification comes from product requirements or story, please refer to this as a bug.