I've been trying to really figure out what components need to be there in a bug report (as a one templte that works for all).This is basically for the sake of building a bug tracking system.
I'm currently interested in deciding on what fields would serve the bug tracking process (i.e: fields that will likely be used by developers, for example)..
project name/id (since u r building system.. assuming that you are going for a common database for all the projects in your company)
status - can also be fixed/reopened
You can also maintain history of updates for every issue.
I say, never be complete.
I say, stop being perfect.
I say, let's evolve..
Thanx alot all;
One more question:
What fields do u think would really serve for clarifying the testing environment ?
i mean, is it okay to add something like "Category" and "Sub Category" and populate them with something like "UI issue", and "Inconsistency"? or shall we populate these with "Coding Issue","Incorrect arithmatic"
i was thinking also of using somthing like "Environment" to indicate that we tested for "Windows XP".
i still feel this is a bit vauge, what do u think?
It depends. It is youself and your superior to decide upon fields. You can fill the details in comment; but if you break it into different fields, it will be easier for search. The key is you have to fill up the fields properly.
He is a true friend who does not forsake us in time of need, misfortune, famine, or war, in
a king's court, or at the crematorium (smasana). - Chanakya