Find Feature of Family Tree - not bringing up expected results
Its seems like the FIND Feature of Family Tree - - is not always picking up correct results. - sort of broke - at least for this specific search.
As an example I search for Richard Kent Watts (1927-2008) ID: KWZ2-HL4
here is the search:
and here is the record in Family Tree:
https://www.familysearch.org/tree/person/details/KWZ2-HL4
Why is it not finding it on the search?
I assume this is some sort of bug - - how do we report bugs - and ensure that such bugs are quickly and effective reported to engineers????
Am I doing something wrong or is this a bug?
If it is a bug - how should bugs be reported?
Answers
-
Sorry to appear pedantic, but wouldn't it be better to retitle this as "FIND feature of Family Tree - not bringing up expected results"?
On your main point, I just tried finding him and had no success, whatever I inputted. Definitely something wrong here. I was told earlier to report possible bugs in "Ideas", not "Q and A", but a little later the opposite was suggested in another Discussion item.
If we could be sure the engineers are visiting "Ideas" that does seem to be the sensible suggestion, but if we can be equally sure a "Q and A" moderator will escalate the problem to the correct department, surely it's fine to post here (That is, to "Q and A - Family Tree" - in case a moderator moves this!)
0 -
BTW - both "Find" and "Search" (at https://www.familysearch.org/search/) both seem "partially" broke right now.
In another thread, a user reported not being able to find an indexed record for an individual in the 1871 E&W census. However, it worked okay for another user (but not me) and the "Search" routine seems fine in getting results for other names from the same collection.
Same thing here - I just entered different names (of my ancestors) in the "Find" section of Family Tree and they appeared at the top of the list. But, as I have said, I tried for Richard Kent Watts without success.
0 -
title corrected.
just seems to me there should be a better way to directly and quickly report bugs to engineers
instead of having hundreds of people see this public post and waste there time all trying to replicate the same thing and various people all escalating . . .
why not just one private submission to engineers.
1 -
Same here.
I have reported similar issues previously. I do global surname studies, where I want all records of a given surname. Repeating searches tends to yield new records and PIDs I did not see before, that have been there, untouched, for years.
0 -
why not just one private submission to engineers.
A few reasons:
- Most private submissions to the engineers in the old case management system were complaints about other contributors changing something, or a user not understanding basic tasks, or demanding that someone fix their tree. So the majority of cases were not cases at all.
- Good case management involves developing cases before the engineers take a look.
- Good case management involves gathering together related cases before the engineers take a look.
- FS Community now is that front-line customer support service.
0 -
Yes - I realize FS community is now the front line support - - just not sure I think its the best fit . . . (the way its currently configured at least) - whereby bug reports - get totally all mingled in with totally unrelated items.
why not have a group/QA area specifically for bug reports / outage reports / system breakages. that we can ensure goes straight to moderators.
1 -
replying to: dontiknow
I agree with your points . . . just wish there was one single entry point for reporting bugs. . . that yes then could be collected, analyzed, consolidated and prepared for engineeers.
Its very confusing now where a bug should be reported - among the plethora of different groups/sections.
1 -
@Dennis J Yancey We appreciate your posting the issue of not being able to find by name, Richard Kent Watts, born in 1927 and died in 2008.
Your question will be forwarded to a specialty team for review and resolution.
You may be contacted by that team if they need to gather more information.
0 -
why not have a group/QA area specifically for bug reports / outage reports / system breakages. that we can ensure goes straight to moderators.
Most contributors making reports are not able to identify what kind of report to make, so triage is necessary.
In the old case management system I was a frequent reporter of bugs and it was a lot of work for me, working in isolation, to persuade a front-line customer support person to escalate. You can see that same challenge here; there are so many responses that are just not on point. And here there is a real downside: many responses are not scripted and some are inappropriately dismissive or utterly wrong. At least here other contributors can step in and assist to contradict wrong responses, clarify the problem, confirm they see it too, and help to make the case for escalating the report.
I must say the mobile app engineering team has been far more on top of user feedback. They had an email for bug reports and after the first few reports I stopped getting boilerplate from the front line. That app has come a long way, and fast!
0 -
I totally understand triage is necessary
but why not put bug reporting under a single Group/Category - I dont think there is anything that says "Report Bugs here" anywhere at all in community is there?? - not a single reference I can find.
can we at least put a label somewhere that says "Report Bugs here" . . . and make it clearly viewable.
0 -
If all issues were reported on one huge stream I would not ever look at it. I only follow the Family Tree group, and then only casually. I have nothing to say about most topics in most groups.
Often the contributor does not know they are reporting a bug.
0 -
I imagine you look at watever you are assigned to look at.
So couldnt a group of moderators be assigned to look at a new group that was set up to be a group for reporting bugs.
I am referring to people who clearly know something is blatantly BROKE and want to let people know so they can fix it - and do so in a manner that is quick and efficient. Or when parts of the system are totally non functional.
But they log on to community - and have 20 or so different groups where they can post items - and no clue where to report bugs - because there is not even a mention of "bug reporting".
0 -
Dennis, the problem is that recognizing a bug is non-trivial, from both ends. When a system doesn't do what a user wants it to do, the user will automatically diagnose it as a bug, but it may in fact be user error, or a design flaw (missing feature), or a momentary glitch, or a configuration error on the user's end, or any number of other things I'm not thinking of.
I feel that this Community already has waaaay too many categories. It's fractured into a million little pieces, and nobody has a clue where their bit should go. Adding yet another one for bug reporting would only add to the confusion.
1 -
Giving Julia a Like.
I like the separate groups for different parts of the FamilySearch experience: Family Tree, Memories, Community, Login account, Library, Search (of historical records), Find (not in existence yet), Partner tools (ditto), Ordinances (ditto)...
That partitioning, consistent with FS components as seen by the user, is recognizable to newcomers. What is not recognizable is Q & A vs Ideas. Collapse Q & A with Ideas, I say, perhaps into Peers Help.
0 -
I imagine you look at watever you are assigned to look at.
Dennis, are you assigned here?
0 -
I wasn't saying there wasn't a need for separate groups - just that one of those groups could be for reporting blatant bugs/things broke etc - that assigned moderators could monitor and report to engineers as appropriate
when I report a bug - I am not expecting it to go to "peers" - Im expecting it to go to moderators - and then if appropriate on to Engineers.
0 -
and it doesnt just have to be "bug reporting"
Im just pointing out that certain submissions are not really intended for "peer help"
Some submissions - such as reporting outages, reporting major bugs, reporting abuse etc are really intended for Moderator response and after their analysis - ultimately for engineers.
Getting all the peers involved on certain posts with all their various opinions - just muddies the water and slows things down some times for the people (moderators/engineers) who really have the power to take action (which peers dont have).
0 -
@Dennis J Yancey we have forwarded your issue regarding the Find Feature not working as expected to a specialty team for review and resolution.
0 -
Thanks so much Idaho!!!!
0
