Coming Soon: Y-DNA Haplogroups for Family Finder

[Mabrams]

I have noticed a few men from 2010 to 2014 who have had their V1 Family Finders updated.

Because these V1 assignments are not very deep, they don't exactly set off any fireworks. Boom!! Some of the men already had SNP Packs or some form of SNP testing, and the V1 did not surpass the present Y haplo.

One guy had a FF from late 2010 and it was updated three weeks ago on July 7.  He had SNP testing in the interim, so there was no change in the Y haplo.  There were approximately 150 Y SNPs from Family Finder listed under the SNP Results button. 

I am not sure how complete the V1 updates are.  I am not aware of any major changes in stats in the last few weeks.

[rmstevens2]

Man! Still waiting on the Y-haplogroup assignment for a guy with my surname who I know did Family Finder in 2021. Taking forever. Probably he won't matter, but I'd like to find out.

[Mabrams]

Man! Still waiting on the Y-haplogroup assignment for a guy with my surname who I know did Family Finder in 2021. Taking forever. Probably he won't matter, but I'd like to find out.

I dont think you can submit a Customer Support ticket for someone else's kit but I guess you could try and see.  Or get your guy to send in a ticket.

If he has a Y37 posted on a project page, you could load that into Nevgen and see if you are still compatible.   


~~~~~

FTDNA has been processing some V1 kits out of chronological order.  At least that's my experience so far.   It seems to me that 2010, 2011, and 2012 kits have been updated.  But not 2013 for some reason.  Or some 2014s.  Not sure how the cut-off ranges, between what month of 2014 down to 2012, but I consistently see 2013s not being updated.   

I did not expect this 2010 to be updated before 2013 etc

As mentioned in above post, many of these updates do not surpass the STR basic prediction.  Although at least it's now a confirmed SNP.  And if there was no STR kit at all, then the update is definitely helpful.

[rmstevens2]

Man! Still waiting on the Y-haplogroup assignment for a guy with my surname who I know did Family Finder in 2021. Taking forever. Probably he won't matter, but I'd like to find out.

I dont think you can submit a Customer Support ticket for someone else's kit but I guess you could try and see.  Or get your guy to send in a ticket.

If he has a Y37 posted on a project page, you could load that into Nevgen and see if you are still compatible.   


~~~~~

FTDNA has been processing some V1 kits out of chronological order.  At least that's my experience so far.   It seems to me that 2010, 2011, and 2012 kits have been updated.  But not 2013 for some reason.  Or some 2014s.   Not sure how the cut-off ranges, between what month of 2014 down to 2012, but I consistently see 2013s not being updated.   

I did not expect this 2010 to be updated before 2013 etc

As mentioned in above post, many of these updates do not surpass the STR basic prediction.  Although at least it's now a confirmed SNP.  And if there was no STR kit at all, then the update is definitely helpful.

All he has is Family Finder.

[ArmandoR1b]

FTDNA has been processing some V1 kits out of chronological order.  At least that's my experience so far.   It seems to me that 2010, 2011, and 2012 kits have been updated.  But not 2013 for some reason.  Or some 2014s.   Not sure how the cut-off ranges, between what month of 2014 down to 2012, but I consistently see 2013s not being updated.   

I did not expect this 2010 to be updated before 2013 etc

As mentioned in above post, many of these updates do not surpass the STR basic prediction.  Although at least it's now a confirmed SNP.  And if there was no STR kit at all, then the update is definitely helpful.

I haven't seen any 2010 kits getting a FF haplogroup.

[Mabrams]

yeah oops...misspoke....

No kits from 2010. I think I only had access to one, which had a BigY.

From 2011 to 2012 I found 5 kits that were updated on July 7 or July 8.
2 to R-L151, 1 to R-M417 and 2 that were J

A lot of my 2011/2012 kits had a BigY. A few had done SNP Packs.

[ArmandoR1b]

yeah oops...misspoke....

No kits from 2010.  I think I only had access to one, which had a BigY.

From 2011 to 2012  I found 5 kits that were updated on July 7 or July 8.
2 to R-L151, 1 to R-M417 and 2 that were J

A lot of my 2011/2012 kits had a BigY.  A few had done SNP Packs.

July 8 is the last day that I see a FF haplogroup assignment. They were a mix of kits from 2011 through 2014.

[JMcB]

Recently, I was pleasantly surprised to see two new German results show up in a cousin branch of mine (F2735) that started forming around 400 AD. With a TMRCA of 800 AD. Naturally, my first reaction was to start looking for new or pending Y700 results because those results are far more refined than most of the FF calls I’ve been seeing. Which usually date to 1200 - 1300 BC in my Haplogroup. When all of those efforts failed, I began to wonder if these testers had put their match settings on Private and that was the reason I couldn’t find them anywhere. So I contacted Family Tree to asked them about it and they told me that F2735 was on some of their earlier FF chips and that’s why I couldn't find them.

As it turns out, I then remembered running into the comments of the fellow who originally tested positive for F2735 back around 2015. When I first began researching my main branch of F2642. He had tested in 2012 and at that time F2735 was the only known SNP below F2642. Which now has 308 branches below it. So I think I got a little lucky in this case. As F2735 is a branch that I’m interested in. Primarily, because it dates to the Middle Ages - along with its parent branch A5487 - and they’re both the first Continental branches under Y7198. Which is currently over 90% British.

[Webb]

A slight correction on my comment that I had announced several times in this thread that R-DF27 people were getting the R-L151 assignment with v2. Of course v1 is not going to be as good as v2 since they added SNPs to the ISOGG tree before v2 was created so some of those were added to v2. R-L21 and R-U152 are almost definitely tested in v1 but just like v2 they aren't providing the negative results. DF27, U152, and L21 are the three big subclades of P312. So most R-L151 would actually be R-DF27 if they had tested for Z195 and ZZ12_1 in both v2 and v1.

FF v2 did test for Z195 but not ZZ12_1. So although most R-L151 would actually be R-DF27 if they had tested for and ZZ12_1 they would be derived for ZZ12_1 which is a subclade of R_DF27. I correctly stated that prior to the last comment but writing that comment in rush caused me incorrectly add Z195.

It is extremely doubtful that Z195 is included in FF v1 though. FF was introduced in May 2010 and Z195 wasn't added to the ISOGG tree until 17 August 2012 https://isogg.org/tree/2012/ISOGG_HapgrpR12.html

There should be evidence soon.

I am not so sure about FF v2 and Z195.  I now show a match from 2012 with a terminal of L151, and as he is a 67 marker match I know for sure he is Z195 and Z209/Z210.  If this is the case, then all kits who are DF27, whether they be under ZZ12 or Z195 will have a terminal of L151.

[Mitchell-Atkins]

A slight correction on my comment that I had announced several times in this thread that R-DF27 people were getting the R-L151 assignment with v2. Of course v1 is not going to be as good as v2 since they added SNPs to the ISOGG tree before v2 was created so some of those were added to v2. R-L21 and R-U152 are almost definitely tested in v1 but just like v2 they aren't providing the negative results. DF27, U152, and L21 are the three big subclades of P312. So most R-L151 would actually be R-DF27 if they had tested for Z195 and ZZ12_1 in both v2 and v1.

FF v2 did test for Z195 but not ZZ12_1. So although most R-L151 would actually be R-DF27 if they had tested for and ZZ12_1 they would be derived for ZZ12_1 which is a subclade of R_DF27. I correctly stated that prior to the last comment but writing that comment in rush caused me incorrectly add Z195.

It is extremely doubtful that Z195 is included in FF v1 though. FF was introduced in May 2010 and Z195 wasn't added to the ISOGG tree until 17 August 2012 https://isogg.org/tree/2012/ISOGG_HapgrpR12.html

There should be evidence soon.

I am not so sure about FF v2 and Z195.  I now show a match from 2012 with a terminal of L151, and as he is a 67 marker match I know for sure he is Z195 and Z209/Z210.  If this is the case, then all kits who are DF27, whether they be under ZZ12 or Z195 will have a terminal of L151.

Just a FYI, Per the bold:  they may testing for U152 but it’s not full proof.   Pre 2012 sample on my U152>>>>>>>>>FGC12384 branch got L151 (sample 132658 was previously labelled M269, and had FF and 37 marker test)

I know there has been a few other U152>>>>Z12222 samples that recently went from M269 to L151

[Webb]

A slight correction on my comment that I had announced several times in this thread that R-DF27 people were getting the R-L151 assignment with v2. Of course v1 is not going to be as good as v2 since they added SNPs to the ISOGG tree before v2 was created so some of those were added to v2. R-L21 and R-U152 are almost definitely tested in v1 but just like v2 they aren't providing the negative results. DF27, U152, and L21 are the three big subclades of P312. So most R-L151 would actually be R-DF27 if they had tested for Z195 and ZZ12_1 in both v2 and v1.

FF v2 did test for Z195 but not ZZ12_1. So although most R-L151 would actually be R-DF27 if they had tested for and ZZ12_1 they would be derived for ZZ12_1 which is a subclade of R_DF27. I correctly stated that prior to the last comment but writing that comment in rush caused me incorrectly add Z195.

It is extremely doubtful that Z195 is included in FF v1 though. FF was introduced in May 2010 and Z195 wasn't added to the ISOGG tree until 17 August 2012 https://isogg.org/tree/2012/ISOGG_HapgrpR12.html

There should be evidence soon.

I am not so sure about FF v2 and Z195.  I now show a match from 2012 with a terminal of L151, and as he is a 67 marker match I know for sure he is Z195 and Z209/Z210.  If this is the case, then all kits who are DF27, whether they be under ZZ12 or Z195 will have a terminal of L151.

Just a FYI, Per the bold:  they may testing for U152 but it’s not full proof.   Pre 2012 sample on my U152>>>>>>>>>FGC12384 branch got L151 (sample 132658)

I know there has been a few other U152>>>>Z12222 samples that recently went from M269 to L151

I was not too shocked that there wouldn't have been a call for ZZ12 on those old FF chips, but to not even have Z195/Z196 was kind of a shock as I believe Z195/Z196 was discovered before DF27.  In fact, if my memory is correct, Razyn was Z196 just after it was discovered that SRY2627 and M153 had that in common upstream, making Z196 the third marker under DF27 that was available for the a la carte snp testing.

[rafc]

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.

[Mabrams]

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)

[rmstevens2]

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)

Right. I see at least two guys with my surname with no Y haplogroup assignment yet.

[ArmandoR1b]

A slight correction on my comment that I had announced several times in this thread that R-DF27 people were getting the R-L151 assignment with v2. Of course v1 is not going to be as good as v2 since they added SNPs to the ISOGG tree before v2 was created so some of those were added to v2. R-L21 and R-U152 are almost definitely tested in v1 but just like v2 they aren't providing the negative results. DF27, U152, and L21 are the three big subclades of P312. So most R-L151 would actually be R-DF27 if they had tested for Z195 and ZZ12_1 in both v2 and v1.

FF v2 did test for Z195 but not ZZ12_1. So although most R-L151 would actually be R-DF27 if they had tested for and ZZ12_1 they would be derived for ZZ12_1 which is a subclade of R_DF27. I correctly stated that prior to the last comment but writing that comment in rush caused me incorrectly add Z195.

It is extremely doubtful that Z195 is included in FF v1 though. FF was introduced in May 2010 and Z195 wasn't added to the ISOGG tree until 17 August 2012 https://isogg.org/tree/2012/ISOGG_HapgrpR12.html

There should be evidence soon.

I am not so sure about FF v2 and Z195.  I now show a match from 2012 with a terminal of L151, and as he is a 67 marker match I know for sure he is Z195 and Z209/Z210.  If this is the case, then all kits who are DF27, whether they be under ZZ12 or Z195 will have a terminal of L151.

Your match from 2012 is on v1 which is from 2010 to the fall of 2015. The v2 chip is fall of 2015 to March 2019. That is another anecdotal example of Z195 missing from v1 which I already had come to the conclusion was missing from v1. So all v1 kits that are DF27 in reality are instead L151 with the FF haplogroup which I warned would happen without Z195.

I have several v2 kits that are downstream of Z195 that show green for Z195 in the haplotree. The v2 kits that are L151 would be ZZ12_1 so they are Z195- even though the result of that SNP is not reported