Reporter:

Product: Survive – browser survival game

Version: Version 1
Component:
Platform:

Operating system:

Priority: P2

Severity:
Me me confused. Clicking on the username shoul open both profile page and user page.
Types of Severity:
● Blocker: No further testing work can be done.
● Critical: Application crash, Loss of data.
● Major: Major loss of function.
● Minor: Minor loss of function.
● Trivial: Some UI enhancements.
● Enhancement: Request for a new feature or some enhancement in the existing one.
Status:
When you are logging the bug into any bug tracking system then by default the bug status will
be ‘New’.
Later on, the bug goes through various stages like Fixed, Verified, Reopen, Won’t Fix etc.
Assign To:
If you know which developer is responsible for that particular module in which the bug occurred,
then you can specify the email address of that developer. Else keep it blank as this will assign
the bug to the module owner if not the Manager will assign the bug to the developer. Possibly
add the manager’s email address in the CC list.
URL:
The page URL on which the bug occurred.
Summary:
A brief summary of the bug mostly in 60 words or below. Make sure your summary is reflecting
what the problem is and where it is.
Description:
A detailed description of the bug.
Use the following fields for the description field:
● Reproduce steps: Clearly, mention the steps to reproduce the bug.
● Expected result: How the application should behave on the above-mentioned steps.
● Actual result: What is the actual result of running the above steps i.e. the bug behavior.