Coming Soon: Y-DNA Haplogroups for Family Finder

[ArmandoR1b]

23andMe and Ancestry Transfers will not be shown to the public, only the uploader.  They do have to be Unlocked.
I did not realize GAP admins would be blocked as well. 

I believe MyHeritage transfers will be shown to all.  I am not sure if they have to be Unlocked. 

~~~~~~

"We’ve completed all the Family Finder Y-DNA haplogroup assignments"
Good to know.....except its not true

I looked at four Family Finders in one project from 2013 and none of them have been updated.  They all have basic haplogroups, like R-M269 etc, from a STR test. 

I looked at another FF from another project, also 2013.  He has not been updated.  Since he has no STR test, he has no haplogroup.


On my personal Y12 match list, I have 137 R-M269 with a true Family Finder test (not an autosomal transfer). 
Why didn't these FF men get updated?  137 is a lot of men to skip.   
I do not know what years these men took the FF (or chip)

I agree that there are a lot of people tested with FF that do not have a FF haplogroup. Some even from 2014. I turned in a ticket for one. Has anyone else turned in a ticket?

[Mitchell-Atkins]

There was a FTDNA newsletter today, which stated that all the Family Finder assignments have been finished.

We’ve completed all the Family Finder Y-DNA haplogroup assignments and will be moving to the transfers soon. Remember, we won’t be displaying the haplogroups of transfers from Ancestry or 23andMe to matches or to Group Project Administrators.

Not sure if this means there are some transfers that will be shown.

That's disappointing.  1327 out of my 3269 12 marker matches remain M269.  Of my 1823 12 marker matches with FF testing, 322 are still M269.


My uncle who's did family finder in 2013 still has no haplogroup assignments.

[Mabrams]

"I agree that there are a lot of people tested with FF that do not have a FF haplogroup. Some even from 2014. I turned in a ticket for one. Has anyone else turned in a ticket?"

Okay, I just sent in a ticket with two kits in question (with their kit numbers) and offered to give several more. 

Both from 2013, one with the STR haplogroup and one with no haplogroup.

~~~~~

Pure speculation.....maybe there are sub varieties of the V1 chip. Maybe not all V1 chips are the same. Perhaps some did not stress the Y. Or extracting the Y data was of very low priority. Or there were QC issues.

I know Ancestry V2 has several sub-versions.

[Riverman]

From Facebook by an admin:

The transfer haplocalls will start processing soon now that all the Family Finder ones are complete.
MyHeritage transfer haplogroups will be visible to admins and matches because they're processed in-house. Ancestry and existing 23andMe ones will only show to the tester.

Therefore they consider FF complete and MyHeritage uploads shouild be next. Any idea about the proportion of MH uploads?

I also have a couple of FF matches which have no assignment below E-M35. Some of which are from common branches of E-V13 (they are from lineages which have BigY-tested members too) which should have been assigned, at the minimum to E-V13.

[ArmandoR1b]

From Facebook by an admin:

The transfer haplocalls will start processing soon now that all the Family Finder ones are complete.
MyHeritage transfer haplogroups will be visible to admins and matches because they're processed in-house. Ancestry and existing 23andMe ones will only show to the tester.

Therefore they consider FF complete and MyHeritage uploads shouild be next. Any idea about the proportion of MH uploads?

I also have a couple of FF matches which have no assignment below E-M35. Some of which are from common branches of E-V13 (they are from lineages which have BigY-tested members too) which should have been assigned, at the minimum to E-V13.

Are they not on v1? I thought that v1 does not have E-V13 and downstream SNPs.

[Riverman]

From Facebook by an admin:

The transfer haplocalls will start processing soon now that all the Family Finder ones are complete.
MyHeritage transfer haplogroups will be visible to admins and matches because they're processed in-house. Ancestry and existing 23andMe ones will only show to the tester.

Therefore they consider FF complete and MyHeritage uploads shouild be next. Any idea about the proportion of MH uploads?

I also have a couple of FF matches which have no assignment below E-M35. Some of which are from common branches of E-V13 (they are from lineages which have BigY-tested members too) which should have been assigned, at the minimum to E-V13.

Are they not on v1? I thought that v1 does not have E-V13 and downstream SNPs.

I don't know which chip they used. Does v1 have nothing between E-M35 and E-V13?

My father has an autosomal Polish match which being assigned to E-P2, I also wondered whether that's the maximum of the v1 assignment for an E-V13, which would be even worse than E-M35. I haven't seen a list for the SNP's v1 covers, but this match was among the last ones assigned, so probably he is on the v1 chip.   E-

[rafc]

Indeed, it seems the V1 E-V13's are classified as E-P2. FTDNA also said in the newsletter that after the transfers are done, they will correct all cases where the assignment led to a less precise group than the STR predictions (all those E-P2's would have been E-M35 STR predicted before).

[ArmandoR1b]

Indeed, it seems the V1 E-V13's are classified as E-P2. FTDNA also said in the newsletter that after the transfers are done, they will correct all cases where the assignment led to a less precise group than the STR predictions (all those E-P2's would have been E-M35 STR predicted before).

That's what I saw too for a person related to other V13 kits based on surname and STR results.

[Mabrams]

FTDNA announced the inclusion of YDNA haplo results on July 31, 2023.  I was going to write something a few days ago, but the posting that updating from Family Finder kits is "complete" (???)  took precedence. 

You can read that the original announcement in message #1 of this thread.  It's interesting to see FTDNA's concept of time.  It was implied that all FF kits would be updated by the end of October, when the Autosomal Transfers would start.  So much for FTDNA keeping to a schedule.  I suppose it was a much larger task than anticipated, and other than being terribly behind schedule, I think it's gone pretty smoothly.  (And don't forget, FTDNA has had to overcome multiple weather disruptions.)

In that time, the FTDNA Haplotree has increased 2.5 fold.  From 230K to 580K.  But since the increase is almost all FF kits, that has really inflated the baser end of the tree, not the advanced end, which is what the Haplotree should emphasize.

I would like to see......
1.  A toggle on the Haplotree, for All Results vs BigY700 only.  Take out the FFs etc.    Or a filter that would work by levels.
2.  A chart, under the three dots on the right, like the Country Report, but this time list tests by Source.  How many of each type (BigY700, BigY500, FF by chip, MH, Nat Geo, SNP Packs, Deep Clade, etc)?
3.  The results of Autosomal Transfers on Family Finder match lists.    What is the point of shielding everyone from data from an AT?  Matches are already tagged Autosomal Transfer, so everyone will know the result is from a transfer. Other than 23andMe v5s, ATs won't be that deep anyway, but they would be moderately helpful.  I do not see the logic behind not displaying Y haplos from ATs.  (I do agree 100% that AT haplos don't belong on the Haplotree or Discover). 

my two cents

[Riverman]

I would like to see......
1.  A toggle on the Haplotree, for All Results vs BigY700 only.  Take out the FFs etc.    Or a filter that would work by levels.
2.  A chart, under the three dots on the right, like the Country Report, but this time list tests by Source.  How many of each type (BigY700, BigY500, FF by chip, MH, Nat Geo, SNP Packs, Deep Clade, etc)?
3.  The results of Autosomal Transfers on Family Finder match lists.    What is the point of shielding everyone from data from an AT?  Matches are already tagged Autosomal Transfer, so everyone will know the result is from a transfer. Other than 23andMe v5s, ATs won't be that deep anyway, but they would be moderately helpful.  I do not see the logic behind not displaying Y haplos from ATs.  (I do agree 100% that AT haplos don't belong on the Haplotree or Discover). 

my two cents

How deep the current FF assignment goes can be extremely variable, like from almost down to the terminal clade in the Medieval/Early Modern period for some, or up to something like E-P2. I think the basic problem of the different levels of testing is much older for FTDNA, because we had all the SNP tested individuals before already, which confused people quite often as to who's SNP vs. BigY tested. The Time Tree solved that for me.

Concerning the latter, I completely agree for the transfers, because how can the assignment of say Ancestry/23andMe/LivingDNA raw data being worse than E-P2? On the contrary, they go much deeper oftentimes than FF v1/2. Like my own 23andMe assignment is so much closer to my terminal clade than E-P2/E-M35 that its not even comparable. And if someone uploads his raw data to FTDNA and finds a namesake or person from the same village with the same basic haplogroup, what could be a better motivation for doing an additional yDNA-test?

[ArmandoR1b]

"I agree that there are a lot of people tested with FF that do not have a FF haplogroup. Some even from 2014. I turned in a ticket for one. Has anyone else turned in a ticket?"

Okay, I just sent in a ticket with two kits in question (with their kit numbers) and offered to give several more. 

Both from 2013, one with the STR haplogroup and one with no haplogroup.

Have you had a response? I was told that by Friday the kit I turned in a ticket for should have a haplogroup.

[Mabrams]

No....not yet     


But I will be interested in hearing if you see an update this Friday on your kit of interest.

[Mabrams]

No....not yet     


But I will be interested in hearing if you see an update this Friday on your kit of interest.

I did get a reply from FTDNA support a few hours after I wrote the above.  At least the support team does look at these tickets.  


For one kit, I gave the wrong kit number.  Off by one row. So that's on me.   Doofus.  A bit embarrassing.   

For the other kit, it will not be updated
" In part because of technical difficulties and also because some of the older Y-DNA clades were not discovered or included in those early tests. "

I think some years were better than others   I found most of the kits that will not be updated to be from 2013.
IMO, FTDNA did a nice job overall on the V2 and V3.   But they should have communicated a few weeks/months ago that the V1 updating was going to be problematic 

[Riverman]

No....not yet     


But I will be interested in hearing if you see an update this Friday on your kit of interest.

I did get a reply from FTDNA support a few hours after I wrote the above.  At least the support team does look at these tickets.  


For one kit, I gave the wrong kit number.  Off by one row. So that's on me.   Doofus.  A bit embarrassing.   

For the other kit, it will not be updated
" In part because of technical difficulties and also because some of the older Y-DNA clades were not discovered or included in those early tests. "

I think some years were better than others   I found most of the kits that will not be updated to be from 2013.
IMO, FTDNA did a nice job overall on the V2 and V3.   But they should have communicated a few weeks/months ago that the V1 updating was going to be problematic 

My hope is with the MyHeritage transfers right now, since among those are a couple of interesting matches. Any news about the start of the assignments for the transfer kits?

[Mabrams]

I have some questions about MH that I have not seen addressed.

Do MH transfers have to be unlocked to be updated?
Will MH transfer updates be shown to everyone, or only to the uploader?
How many estimated MH transfers are there? Must be V2, no V1s
Are MH transfers currently labeled with the gray 'Autosomal Transfer' tag at FF?

The only thing that I remember from FTDNA blogs is that MH updates will be added to the FTDNA Haplotree, since they were processed by FTDNA.

I know on my branch of R1b, the MH haplotype (Z9) that I anticipate based on an Armando earlier post, is much better than a FF V1, but a lot less than FF V2/V3. It could be useful to rule-out but a bit broad to be a reliable rule-in.