Open Bug 16979 Opened 20 years ago Updated 13 years ago
Go|First Flagged Message
This bug is used to track the implementation of Go|First Flagged Message
Reassign to putterman for M15 (or thereabouts)
Moving all P4s out of beta2 to M17.
Target Milestone: M16 → M17
[FEATURE] bugs past M16 are OUT for this release. Marking M20. If you disagree with this action, please help me explain it to the PDT.
Target Milestone: M17 → M20
once again, this is a feature only in the sense that it's a line item on a schedule. It should be easy to do this. If we don't want the menuitem then this is a different story, but if we're removing this solely because it has the word feature on it then I think that isn't necessary.
Target Milestone: M20 → M17
this is more of a bug than a feature. We already have the ability to navigate to the first flagged message. It's just not hooked up to the menu.
Summary: [FEATURE] Go|First Flagged Message → Go|First Flagged Message
After all of what I wrote I'm still moving to future milestone. :)
Target Milestone: M17 → Future
Bug 45201 to remove menu item.
reassigning to sspitzer
Assignee: putterman → sspitzer
Status: ASSIGNED → NEW
At this point, this bug is clearly about adding a feature. I don't think TB would bother with what is an 'expert' level function (Go|Next|Flagged -- or rather, 'Starred' -- is implemented, except see bug 81091). Comment 5 indicates that this is not a backend issue, so moving to suite/front-end.
Assignee: sspitzer → mail
Severity: normal → enhancement
Component: MailNews: Backend → MailNews: Main Mail Window
Priority: P4 → --
Product: Core → Mozilla Application Suite
QA Contact: laurel
Target Milestone: Future → ---
You need to log in before you can comment on or make changes to this bug.