Closed Bug 1778004 Opened 5 months ago Closed 4 months ago

Address book horizontal lost per-type columns for email addresses (work, home, none) - only has one-for-all column `Email Addresses`

Categories

(Thunderbird :: Address Book, defect, P4)

Thunderbird 102

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: schoen, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0

Steps to reproduce:

Open Address book and set to horizontal view

Actual results:

All types of email (home, work, none) have been merged into a single column.

Expected results:

There needs to be a column for each type of email as there was in previous versions. As a bonus, there could also be a option for a column that shows the merged list of emails now shown.

Yeah, the old AB had dedicated column for Email vs. Additional Email, so by analogy, separate columns for Work, Home, none may still be useful.

Severity: -- → S4
Component: Untriaged → Address Book
Keywords: regression
Priority: -- → P4
Summary: Address book horizontal view email address now have merged content → Address book horizontal lost per-type columns for email addresses (work, home, none) - only has one-for-all column `Email Addresses`
Blocks: tb102found

Sorry, I don't think this is worth implementing.

Status: UNCONFIRMED → RESOLVED
Closed: 4 months ago
Resolution: --- → WONTFIX

Sorry to hear that you don't think this is worth fixing. I would think that this should not be difficult to implement assuming email data has not been blended in an unfortunate way. If the data has been mixed in a way that it makes it difficult to separate out, then this suggests to me a deeper issue that may lead to other support problems.

The main issue is that the data can now be much more complex (we now support more complex data, and more than 2 addresses). There would not be 1-2 addresses, but there could be 20 different addresses with or without types.

You need to log in before you can comment on or make changes to this bug.