Open Bug 482492 Opened 11 years ago Updated 9 years ago

Feedback/Alert notifications need category information

Categories

(MailNews Core :: Backend, defect)

defect
Not set

Tracking

(Not tracked)

People

(Reporter: standard8, Unassigned)

References

(Blocks 1 open bug)

Details

At the moment the feedback/alert notifications only have the information that
is in the error message, e.g. "Failed to connect to server xxx".

We need some sort of category/classification of what the errors/messages are so that alerts can be appropriately displayed.
Flags: blocking-thunderbird3+
Whiteboard: [b3ux]
Status: NEW → ASSIGNED
Whiteboard: [b3ux] → [b3ux][m4]
David (Ascher) do we want this for poptarts, or should we move it to wanted?
Whiteboard: [b3ux][m4] → [b3ux][m4][still blocking?]
Whiteboard: [b3ux][m4][still blocking?] → [b3ux][m5][still blocking?]
Whiteboard: [b3ux][m5][still blocking?] → [b3ux][m6][still blocking?]
Summary: Feedback/Alert notifications need category information → [poptarts] Feedback/Alert notifications need category information
Priority: -- → P5
Still not sure if I need this for some other bugs. Moving out to b4 for now though.
Whiteboard: [b3ux][m6][still blocking?]
Target Milestone: Thunderbird 3.0b3 → Thunderbird 3.0b4
Summary: [poptarts] Feedback/Alert notifications need category information → Feedback/Alert notifications need category information
Whilst we need probably need this at some stage for alerts, it isn't actually blocking any current Thunderbird 3 work, therefore taking off of the blocking list.
Flags: blocking-thunderbird3+ → blocking-thunderbird3-
Target Milestone: Thunderbird 3.0b4 → Future
Assignee: bugzilla → nobody
Priority: P5 → --
Target Milestone: Future → ---
This is a mass change. Every comment has "assigned-to-new" in it.

I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.