Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

...

  1. Description - should be as much detailed as possible. Might contain printscreens, steps how to reproduce the issue

  2. Assignee - assign the bug to the developer immediately

  3. Label - not required however it helps you to filter all your bugs when needed

Example

Jira Legacy
serverSystem JIRA
serverId0e65890b-f559-36c3-b4f7-807e5b0df1a0
keyC4MICHAMN-255

...