Closed Bug 43484 Opened 25 years ago Closed 25 years ago

Order of accounts in Mail folder pane and Account Settings

Categories

(SeaMonkey :: MailNews: Account Configuration, defect, P1)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jglick, Assigned: alecf)

References

(Blocks 1 open bug)

Details

(Whiteboard: [nsbeta3+][UE1] Fix in hand [usability])

"Local Folders" should always be the last account level item in the folder pane. All Mail accounts should come before all News accounts. Order: Mail Accounts (in order added, default is generally first, unless later changed) News Accounts (in order added) Local Folders
nominate as nsbeta3
Keywords: nsbeta3
Target Milestone: --- → M18
QA Contact: lchiang → nbaca
Ninoschka - don't we have another bug against alecf on ordering of accounts in the folder pane?
Marking bug# 28633 a duplicate of this one. Bug# 28633 states that the accounts are in arbitrary order and explains that the order in Account Settings and the Folder pane do not match. This bug gives more directions on what order the accounts should be. We should also make sure that the order of accounts displayed in Account Settings matches the order displayed in the Folder pane.
Summary: Order of accounts in Mail folder pane → Order of accounts in Mail folder pane and Account Settings
*** Bug 28633 has been marked as a duplicate of this bug. ***
this is an account manager bug, reassigning to me.
Assignee: putterman → alecf
Component: Mail Window Front End → Account Manager
Status: NEW → ASSIGNED
Set to Priority 1 based on UE review meetings.
Priority: P3 → P1
Opps, my error. After meeting with Mail team, order should be: All Mail Accounts (default account at top, then in order added), Local Folders, All News Accounts (in order added).
Keywords: mail2
+ per mail triage If Jennifer's solution is hard to implement, is there a way to have the default mail server always be at the top of the folder pane?
Whiteboard: [nsbeta3+]
jennifer's solution is easy, I'll do that.
Whiteboard: [nsbeta3+] → [nsbeta3+]Fix in hand
Whiteboard: [nsbeta3+]Fix in hand → [nsbeta3+][UE1] Fix in hand
the one thing about the fix I'm about to checkin is that it doesn't update the order when someone clicks on the "set as default" button, but that should go in another bug, and probably doesn't need to be nsbeta3'd
fix is in
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Whiteboard: [nsbeta3+][UE1] Fix in hand → [nsbeta3+][UE1] Fix in hand [usability]
jennifer, you saw this was already fixed, right? :)
Yah, I saw it was fixed! :-) I thought if folks wanted to do a search for the usability bugs and see their status (how many fixed, how many still open, etc.), it would be good to include the fixed ones also. That way, people can see how good the mail folks are at getting stuff fixed! :-)
Adding ue1 because i felt like it? akin to dveditz@netscape.com's nsbeta2/nsbeta3 keyword mass spams.
Keywords: UE1
Build 2000-08-25-08M18: NT4, Linux 6.0, Mac 9.04 It's working much better! 1. Mail folders appear first, followed by Local Folders and then News accounts. 2. Changing the default mail account - When changing the default mail account (i.e. to qatest33) the change is not reflected immediately in Account Settings, close the dialog. - It is not reflected in the Mail folder pane - Open Account Settings and now the new default account (qatest33) is at the top of the list, close the dialog. - The mail folder still does not reflect the change - The change appears after: - Mail is closed and opened again via Navigator, then switch back to Mail. - Exiting and restarting Mail. Question: Can we make the change sooner or should I log another bug to address item 2 for the next release.
yeah, let's deal with it in a later release... new bug!
Verified Fixed. Issue #2: For the new default mail account to appear first and immediatley is logged in bug# 50841.
Status: RESOLVED → VERIFIED
Blocks: 61078
Keywords: UE1
Fixing this bug broke bug 10215
Blocks: 155951
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.