Some of the PMs or customers don’t want to have bugs reported as “BUG” as they report it this way themselves. In such case there is possibility to report bugs as sub-task.
What
creating bugs in sub-tasks instead of BUG types
Why(purpose)
Sub-tasks with a defect for better defect handling between QA analyst and configuration engineer.
Approach made work for developers easier. They can fix defect after they will have time and not jump from one think to another. Approach for not losing context of found issues.
Where
create sub-task under original task/user story
How
Open original user story where you want to create a sub-task, write a short description of the sub-task and save.
When the sub-task is created following information needs to be filled:
Description - should be as much detailed as possible. Might contain printscreens, steps how to reproduce the issue
Assignee - assign the bug to the developer immediately
Label - not required however it helps you to filter all your bugs when needed
Example
C4MICHAMN-255 - Getting issue details... STATUS
C4MICHAMN-239 - Getting issue details... STATUS
NOTES:
Not for all defects were created sub-tasks. Some of the defect were handled immediately with developers or in comments.
Defects are possible to manage in sub-tasks (report). When defects are written in comments it is not possible to do it.
logging bugs as bugs or sub-task is important to keep track of the ongoing issues which are easily lost in comments
In case there are also sub-tasks created for recording test results there might be kept some differentiation in description already (e.g. write BUG on the beginning of every description, see examples above)