Closed Bug 1771576 Opened 2 years ago Closed 2 years ago

[meta] Ensure that all contact fields of TB 91 are migrated (somehow) into TB 102, to avoid (perceived?) dataloss

Categories

(Thunderbird :: Address Book, defect, P2)

Thunderbird 102

Tracking

(thunderbird_esr102 unaffected)

RESOLVED FIXED
107 Branch
Tracking Status
thunderbird_esr102 --- unaffected

People

(Reporter: thomas8, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: dataloss, meta, regression)

+++ This bug was initially created as a clone of Bug #1771569 +++

We need to check if we're really migrating all fields of a TB 91 contact into TB 102. I bet we've overlooked some, like Custom 1-4 fields, Notes etc.

Urgent as it needs strings.

Can we have someone from AB-devs listing all contact fields here which are correctly migrated?

Summary: Ensure that all contact fields of TB 91 are migrated (somehow) into TB 102, to avoid dataloss → Ensure that all contact fields of TB 91 are migrated (somehow) into TB 102, to avoid (perceived?) dataloss
Depends on: 1771824
Blocks: tb102found

We're 2 weeks away from the final 102 and we're working on restoring the custom fields.
Please, don't needinfo me unless it's a bug or a technical issue. Continue using the mailing list for these kind of discussions.

Flags: needinfo?(alessandro)

Migration of Department field has weird behaviour per Bug 1777780 resulting in multi-line Organization field, which is then split up in unpredictable reverse ways to fill ghost Department column and Organization column in horizontal view - we really need to restore a dedicated Department field as in TB 91.

Depends on: 1777780
Priority: P1 → P2

(In reply to Alessandro Castellani [:aleca] from Bug 1776129 comment #3)

Plan for 102

Add back those custom fields that had any data in it, as static and always present so users that had data can still see it and edit it.

After 102

Convert those custom fields to actual repeated custom fields and implement those properly based on the vcard spaces.

Regarding all other vCard4 fields we're currently missing, we will implement those after 102.
No need to over engineer or complicate things.
The work on the address book isn't complete and this is a weird transition period.

Depends on: 1776129
Keywords: meta
Summary: Ensure that all contact fields of TB 91 are migrated (somehow) into TB 102, to avoid (perceived?) dataloss → [meta] Ensure that all contact fields of TB 91 are migrated (somehow) into TB 102, to avoid (perceived?) dataloss
Depends on: 1789990

All blockers of this have been fixed on daily.
Can we close this?

Flags: needinfo?(bugzilla2007)

I have added bug 1786677. I don't see any others to be added from https://mzl.la/3U6zOE6

However, I remember seeing an issue mentioning nickname - I don't remember if it was on reddit, sumo or somewhere else. And I can't find it.

Depends on: 1786677

My TB automatically updated to version v102.2.1 on the update channel.
It converted my address book and now I'm missing all "Screen Name" data.
How could v102.2.1 have been released? This was a blocking issue for version 102.

Now please help me in recovering my data. It has been painstakingly collected over many years.
I need to save the old data (all fields including "Screen Name") to a .csv file.

Please help me get my data back?

Flags: needinfo?(bugzilla2007)

What's the "Screen Name", do you maybe mean "Display Name"?
If so, that's available and editable, and you can decide if to show it or not.

Can you share a screenshot of your missing data?

Flags: needinfo?(martinr1111)

I think he's talking about the instant messaging screen names which we didn't show (but do now, bug 1789990).

(In reply to Alessandro Castellani [:aleca] from comment #8)

What's the "Screen Name", do you maybe mean "Display Name"?
If so, that's available and editable, and you can decide if to show it or not.

Can you share a screenshot of your missing data?

I did an analysis of the vcard data that was exported and compared it to an old pre v102.2.1 .CSV export in order to derive what information appears to be missing:

Old pre v102.2.1 data fields in an old .csv export (and occurence in post v102.2.1 vcard data export):
1 First Name
2 Last Name
3 Display Name
4 Nickname
5 Primary Email
6 Secondary Email
7 Screen Name (MISSING post v102.2.1)
8 Work Phone
9 Home Phone
10 Fax Number
11 Pager Number
12 Mobile Number
13 Home Address
14 Home Address 2
15 Home City
16 Home State
17 Home ZipCode
18 Home Country
19 Work Address
20 Work Address 2
21 Work City
22 Work State
23 Work ZipCode
24 Work Country
25 Job Title
26 Department
27 Organization
28 Web Page 1
29 Web Page 2
30 Birth Year MISSING (in another format now)
31 Birth Month MISSING (in another format now)
32 Birth Day MISSING (in another format now)
33 Custom 1
34 Custom 2
35 Custom 3
36 Custom 4
37 Notes

I reverse engineered the new data fields that seem to have appeared in the new data model in the VCARD export (.CSV export doesn't work in v102.2.1):
New fields as it seems in v102.2.1:

Chat Accounts (+): IMPP:TEST_chat_Accounts, IMPP:TEST_chat_Accounts2
(Org) Role: ROLE:TEST_Role
Phone Numbers (+): TEL;VALUE=TEXT:TEST_phone_no_none
Email (+): EMAIL:TEST-Add_email_address
Website (+): URL:https://TEST-WEBSITE

(the + denotes 1 or more entries possible)

So there you have it. IMPP fields are unpopulated and the "Screen Name" field is missing in v102.2.1.

Flags: needinfo?(martinr1111)

Thanks for the info and the data analysis.
I see you're part of the conversation in bug 1789990, which indeed re-enabled the showing of that data. I can confirm that no dataloss actually happened, and was simply a UI mistake.
It should be on 102 in the next couple of weeks with a new update.

Closing this with a FIXED since it doesn't seem to be any missing field between 91 and 102.
We can always reopen it if something comes up.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 107 Branch
You need to log in before you can comment on or make changes to this bug.