-
Notifications
You must be signed in to change notification settings - Fork 2
Doc.Policy.Issues
Haydar Mehryar edited this page Mar 11, 2023
·
2 revisions
- An issue is an atomic task.
- Atomic means that it can not be split into smaller tasks. for example, calculating for the kinetic energy, K=1/2mv^2, is a function that takes two inputs (mass, and velocity), and after calculating it returns the output (K).
- It normally will be created when the research group planning to do/implement a new module.
- by making small issues, you can relate these small units to each other to reach the purpose of the milestone.
- Issue-code: The issue number should look like "GRUP.XX.FR.XX.", The group name should be abbreviated in 4 capital letters. Please refer to milestone policy page for it. The first XX is for milestone number in the according to the group, the second XX is for the functional requirement number in the milestone
- Description: A complete description of the issue, what problem it is solving, what would be the probable test to check the functionality of the issue.
- Version: is the release that this issue is going to be part of it and in its test plan.
- Creation Date: is the date that issue has been created in the format like mm/DD/YYYY
- Priority: can be 1 as highest, 2 as medium, and 3 as lowest.