User should be able to create a defect either from a
project , task or directly from the LHS menu.
The fields to be captured are described in the issue raised for the main requirement . Listed again down are the fields
a. Id – Autoassigned - Numeric
b. Project – Auto filled / select from a drop down
c. Release Number – Release number of the current release (this is auto filled or can be made optional)
d. Created by –Auto filled User Id (of the user creating the defect) - Mandatory
e. Created on -Auto filled with current date-time - Mandatory
f. Updated by – User Id - Mandatory
g. Updated on – Date Time - Mandatory
h. Title (100 chars) -Madatory
i. Description -Mandatory
j. Status (Auto filled to New)
k. Steps to reproduce (A Text box , where the user can enter the detailed steps on how to reproduce the bug)
l. Requirement : A drop down to choose from (This is optional)
m. Upload a document
n. Priority - Mandatory field (P1, P2, P3, P4)
o. Severity – Mandatory field (BLOCKER, HIGH , MEDIUM, LOW)
p. AssignedTo - drop down of users from the project (user can select a member )
q. Environment - Optional
r. Functional Category -Optional
s. Root cause – Mandatory if value in status is RESOLVED, FIXED or CLOSED. (from a drop down – The drop down will have the following items
i. Requirements
ii. Design
iii. Coding
iv. Data
v. Deployment
vi. Environment
and this list of items should be configurable i.e., user should be able to add more values later if needed._
t. Resolved Date
u. Resolved By
v. Closed Date
w. Closed By
x. OS - Mandatory (Windiws/OS)
y. Browser – Mandatory (if not pplicable , shouls be set to N/A) - IE, FIrefox, Chrome , Safari, Chromium, Netscape, NA
z. Additional Notes: Text area (Optional)
User should be able to create a defect either from a project , task or directly from the LHS menu.
The fields to be captured are described in the issue raised for the main requirement . Listed again down are the fields
a. Id – Autoassigned - Numeric b. Project – Auto filled / select from a drop down c. Release Number – Release number of the current release (this is auto filled or can be made optional) d. Created by –Auto filled User Id (of the user creating the defect) - Mandatory e. Created on -Auto filled with current date-time - Mandatory f. Updated by – User Id - Mandatory g. Updated on – Date Time - Mandatory h. Title (100 chars) -Madatory i. Description -Mandatory j. Status (Auto filled to New) k. Steps to reproduce (A Text box , where the user can enter the detailed steps on how to reproduce the bug) l. Requirement : A drop down to choose from (This is optional) m. Upload a document n. Priority - Mandatory field (P1, P2, P3, P4) o. Severity – Mandatory field (BLOCKER, HIGH , MEDIUM, LOW) p. AssignedTo - drop down of users from the project (user can select a member ) q. Environment - Optional r. Functional Category -Optional s. Root cause – Mandatory if value in status is RESOLVED, FIXED or CLOSED. (from a drop down – The drop down will have the following items i. Requirements ii. Design iii. Coding iv. Data v. Deployment vi. Environment and this list of items should be configurable i.e., user should be able to add more values later if needed._ t. Resolved Date u. Resolved By v. Closed Date w. Closed By x. OS - Mandatory (Windiws/OS) y. Browser – Mandatory (if not pplicable , shouls be set to N/A) - IE, FIrefox, Chrome , Safari, Chromium, Netscape, NA z. Additional Notes: Text area (Optional)