User Story [was Re: Triage Plan for Firefox Components]

I have found it helpful when this editable field is used as an up
to date summary of the bug and its state.  I don't know why it
is called "User Story" rather than "Summary", but this use doesn't
seem at conflict with the purposes described in bugs 879385 and 895687.

If the report is tracking a feature, then the summary tracks the
feature and what is required for that.  If it is tracking a bug,
then the summary tracks what is known about the bug and what is
required for it to be fixed.

Emma Humphries writes:

> You're using a field intended for describing features to be a bug summary,
> which it's not. And this is part of what's driving this work. We have a
> couple of hundred components making up Firefox in Bugzilla and multiple
> teams all using Bugzilla in slightly different ways, so that it becomes
> increasingly difficult to understand what's going on without non-trivial
> insider knowledge.
>
> -- Emma
>
> On Thu, Apr 7, 2016 at 6:41 AM, Philip Chee <[email protected]> wrote:
>
>> On 07/04/2016 14:50, L. David Baron wrote:
>>
>> > (I'd much rather a bug report be editable text, with history
>> > available, for answers to these or similar questions -- rather than
>> > a stream of permanent comments.  But we seem stuck with the horrid
>> > stream-of-comments Bugzilla format, which means I try to ignore the
>> > comments as much as I can.  Then again, a 200 character summary is
>> > often good enough to answer the above 5 questions.  As with the rest
>> > of the Internet, don't read the comments.)
>>
>> I'm currently using the "User Story" text area to provide an up to date
>> summary of the state of the bug. This works great since it's editable.