[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[eclipse.org-architecture-council] [Bug 288393] New: Bugzilla best practices: assigning bugs to '-triaged' should be done via a status instead
|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=288393
Product/Component: Community / Architecture Council
Summary: Bugzilla best practices: assigning bugs to '-triaged'
should be done via a status instead
Classification: Eclipse Foundation
Product: Community
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Architecture Council
AssignedTo: eclipse.org-architecture-council@xxxxxxxxxxx
ReportedBy: denis.roy@xxxxxxxxxxx
--- Comment #0 from Denis Roy <denis.roy@xxxxxxxxxxx> 2009-09-02 13:52:21 EDT ---
I've been getting emails like 'in accordance to the architecture council's
bugzilla best practices, we should use assign bugs to the
"your-component-triaged@xxxxxxxxxxx" user to indicate that the bug got initial
triage.'
This has the potential to turn into a whole bunch of work for the EMO.
With Bugzilla 3.4, we can add a TRIAGED state that could fit in the Bug
workflow, between NEW and ASSIGNED. IMHO, this would be both more elegant
(i.e, searchable, and truly representative of a bug's state) than assigning to
a bunch of dummy inboxes.
--
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.