> We are using summary field because of the following reasons :-
> - Cross verification with talkback server to get reproducible
> steps.
> - Helps to track down topcrash bug.(with topcrash keyword
> combination).
> - Helps to provide topcrash list with appropriate and accurate
> bug status in the Topcrash reports.
> (eg.
> ftp://ftp.mozilla.org/pub/data/crash-data/seamonkey-crash-analysis.txt)
None of these require you to use the _summary_ field! You could use Status
Whiteboard and still have all of this.
> - Avoid duplication .
But _creates_ a great deal of duplication because people don't see "Crash
when I open the Address Book" in the mostfreq list, they see "Crash in
[FooBarBaz::OnStateChange]", and so file a bug with the title "Crash in
the Address Book", which gets duped against the first one, and the cycle
continues.
> - We don't have access to bugzilla database.
Why do you need it?
> - No other customizable field available.
Status field.
> - Size of the summary field is morethan 30 characters.
> Status field is used for various other reasons.
It can be used for those too. That's what regexps are for.
> And it is limited to 30
> chars max.
This is simply not true! I just did a test and successfully set this field
to a string which is 100 chars long.
Gerv
