Wrong assignment after upgrade Geno 2.0 - mtDNA FGS

[GaryStebbins]

Thank you, Darren. It appears the matches are correct. I didn't expect to see that many, and jumped to the conclusion there was still a problem.

Gary

[Darren]

Hello,

I sent you an email.

-Darren
Family Tree DNA

[GaryStebbins]

The bug seems to be back in a different form. Now I'm seeing 17 matches on HVR1+HVR2, but 229 matches when I add in Coding Regions. All matches show as J1c2. (Kit B40340)

Darren, JeremyB, help again, please!

[jarlmos]

Thanks

Thank you Darren and JeremyB. I am now correctly placed in haplogroup V.

[GaryStebbins]

Thank you Darren and JeremyB for following up on this bug.

[Bartot]

It almost sounds as if FTDNA did not plug in your differences from the CRS,leaving you with the CRS haplogroup H2a2a1.

since natgeno are using the latest #16version mtdna trees since March 2015 on their site, Ftdna will not accepted any marker which does not appear on the #14version mtdna trees which they use.

so when you transfer, ftdna will use from your data what fits the mtdna they use

[JeremyB]

Family Tree DNA IT/Engineering reports that they have a fix for the site bug that is causing this issue. They will push a fix sometime this afternoon or early tomorrow.

Jeremy B.
Senior Agent
Family Tree DNA

https://www.familytreedna.com

[GaryStebbins]

Darren, thank you for following up. I sure hope this bug gets squished soon.

[Darren]

I spoke with management today and they are following up with engineering to get this thing moving along. It sounds like it may be more complex than originally anticipated and I do not yet have an estimated time frame. I am sorry for this.

-Darren
Family Tree DNA

[Darren]

Hello,
I am going to follow up with management and see what is going on.

-Darren

[GaryStebbins]

This problem is still occurring. Darren or JeremyB, is there any additional information about when it might be fixed? This is a pretty serious bug, and it's been going on for over a month now.

Thank you.

[Darren]

Hello,

I followed up with the engineering team on this and it is currently one of the highest priority bugs they are working on. While I have no specific time frame for a correction they want to have it fixed very soon. I am sorry for this continued inconvenience.

-Darren
Family Tree DNA

[jarlmos]

The same problem

I have the same problem. I am Haplogroup V and have been misplaced in H2a2a1 and it is 3 weeks ago I contacted Customer support. I share trifud's frustration.

[trifud]

I reported this bug a month ago but they haven't fixed it yet.

[GaryStebbins]

Another H2a2a1 result...

I see JeremyB acknowledged a problem with this result. I just got my mtFullSequence results back, and was quite surprised that I matched over 400 people at HVR1+HVR2+CodingRegion. Now I understand this is false (which I sort of suspected).

JeremyB, 6 days ago you said this would be addressed ASAP. Can you give an estimate in days (or fortnights)?

Thank you.

Gary