Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Close to Record Numbers of Bugs

I would like to award the Woody Brison Amazing Performance Award to the Family Search team for an extraordinary quantity and creation rate of bugs.

A few years ago, I was on the design team that built the Mars Reconnaisance Orbiter. I worked with a computer program called HDL Designer, and I found a bug. I wrote down a description. Then I found another bug, and I added that to the file. I kept doing this because I didn't know where to report bugs. Eventually I had over a hundred bugs documented. I sent the file to their Sales and Cheerleading Rep. And nothing ever happened. Not a single bug in my list ever got fixed. Reasons (I ween):

1. A big enterprise is like the mythical Brontosaurus. Huge body marching along, tiny brain, long long message channel. Brains sez stop. turn left. Legs just keep marching...

2. Nobody wants to be the bearer of bad news. That poor Sales and Cheerleading Rep, faced with the choice between a) submitting a list of over 100 bugs in their flagship product, or b) pushing it into the trashcan as far down as it would go... chose (b)

I worked with FS/FT for a week and compiled a file of 33 bugs in just 7 days. I despair of there being any place to submit bug reports and have them be effective, so I just dropped the endeavor. A few months later I started logging again, the bugs that I found for a week, this time I got 10 more.

It's disheartening and disappointing, when I think of all the people using Family Search and pouring their efforts into it heart and soul, and this seems to be unmatched by the invisible folks on the other end. I don't expect it's a lack of effort on their part; I think they just don't know what to do.

Why not go to Google and ask them how they do this kind of stuff? Or ask them to do it for us?
Reply
  • Woody, since you have the experience to fix this kind of thing, why don't you volunteer to work as a missionary on fixing the bugs. That way, they could get fixed and you would not have any reason to complain without being specific.

    Compiling a list is one thing, but being specific is quite another.
    • I would love to serve such a mission but Tom, I'm reluctant to go to work fixing bugs because fixing one or ten, won't fix the problem, it seems to me. We already have what, 400 coder minions? one more would be an increase of a quarter percent...

      But I doubt anybody in FS mgmt would assign me to any position with enough clout that I could fix the real problem. There is some reason why they keep getting created.

      Micro$oft has a paradigm and a mission. The paradigm: "It's impossible to write bug-free software." And their mission is to prove this. I believe their problem is rooted in step 1: you gotta care.

      Step 2: you have to be willing to see the bugs.

      Step 3: you have to zoom out and find the real problem, starting with your charter and working down.

      I don't think the diagram at this link will help, surely not?
      https://dilbert.com/strip/1995-11-13
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • EMPLOYEE
    I’m Happy
    Woody,

    Thank you for taking the time to express your frustration.  The quality of our products is important to us and we welcome any feedback you may have.  Here are ways you may provide details on issues with our site:
    1. The footer on the bottom of our site pages has a Feedback link (I assume that is how you submitted your post).  You then select if your comment is a Praise or a Problem.  You selected Praise.  If you select Problem, you are presented with a simple form that allows you to report the problems you are experiencing.  Our Product Owner reads all feedback that comes through this page.  We prioritize all reported problems and fix them as prioritized.  We welcome your feedback anytime.
    2. Unlike many other sites, FamilySearch offers free phone support at 866-406-1830. If you prefer to describe your issues over the phone, we are there to listen and help 24-hours a day.
    Our purpose is to "create inspiring experiences that bring joy to all people as they discover, gather, and connect their family -- past, present, and future." As a non-profit, we work to do it for you at no cost.  We appreciate your feedback and any recommendations you wish to provide.

    Have a great day!

    Steven Weitzeil
    FamilySearch Engineering
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Steven

    Firstly, users come here with their problems because they have often had an exasperating experience when trying to resolve a matter by telephone. Unless things have changed fairly recently, I suggest you ring Support with anything other than the most basic of queries and see how satisfactory the experience is.

    Secondly, if your colleagues are reading all these posts - especially the ones that report bugs - how much extra time would it take for them to type-in a comment showing the matter is acknowledged and will be dealt with asap? Currently, the only employee who regularly tries to do this is Joe Martel and obviously he is not responsible for the actual resolution of the issues.

    Tom Huber, and others, clearly listed the many bugs that occurred after the major update of Family Tree last year, as well of the more limited number that seem to appear following even minor updates. Thankfully, many of these are quickly fixed, but our important work in Family Tree is regularly made very difficult (and even held up) by the creation of bugs. The consensus amongst users appears to be that many of the past problems could have be avoided if sufficient user testing had been carried out in the Beta program. However, other problems seem to arise because of the lack of coordination between one FamilySearch (development) section and another.

    For a brief period your colleagues DID involve themselves with threads on this forum and users were very appreciative in knowing various glitches were being addressed. Sadly the communication position seems to have worsened considerably in recent months and we rarely get updates (apart from fellow users who are not employees) - even to advise a reported problem has been fixed.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Amen to Paul's comments above.

    STEVEN, welcome (back) to the forum and for the reminders of how to make forum feedback, phone support and FS goals.

    Perhaps if you would review a few more posts herein you might find that most posting have (and are) providing a great deal of what should be useful feedback for you.

    If your profile is correct, you have posted and are 'following' 57 topics - the vast majority of which appear to be 8 years ago, when you joined the forum.

    https://getsatisfaction.com/people/st...

    It's always good to hear employee feedback and we look forward to more responses and answers to suggestions.

    Have a great day!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Paul,

    Woody's statement was, "I didn't know where to report bugs.". I answered the question with no intention to imply the services are perfect. Thanks for your feedback and passion.

    No one wants our products and services to be without flaw more than those who work on it. We all have the same desire you do and welcome your constructive feedback. Please forgive us if we don't have the time to provide a personal response to every single request and idea.

    Steve
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Steven

    ( I prepared this response to your post straight after you responded the other day; but, decided to hold off to await other responses ... )

    Welcome back to this "FamilySearch" ("GetSatisfaction") 'Feedback' Forum.

    It is really truly great to know that members of the "Engineering" (ie. "Programming") Team of "FamilySearch" do personally monitor this Forum.

    You joined this Forum back in 2010; but, have not posted for over 2 Years - we understand why, you must be so very busy with all the (too) many 'competing priorities' in "Family Tree" and "FamilySearch"; and, be hamstrung with the very 'limited resources' within "FamilySearch" - we really do.

    We totally understand that, the monitoring of; and, the participation in, in this Forum, by those like yourself, is not actually part of your, work; and/or, calling.

    But ...

    That said ...

    'Woody' was definitely 'tongue in cheek' by posting this post as "Praise".

    But, his FRUSTRATION is mirrored by, not only the, many, many Users/Patrons (both, Members of the Church; and, non-members) who regularly participate in the Forum; but, also by many, many Users/Patrons (both, Members of the Church; and, non-members) who do not participate in this Forum - And, I am only taking about those from the Stakes/Wards/Branches of the Church; and, also those who attend the "Family History Centres" (FHCs) of the Church throughout the World.

    I know and am certain that your response to 'Woody's' post here, was not meant to be condescending; but, the to many of us (as outlined above), it can be misconstrued and taken as such.

    'Woody', like many of us 'lowly' Users/Patrons, has in the past; and, does continue to, extensively (ie. already) provide 'Feedback' through this Forum.

    How else would 'Woodly' (and the many of the 'lowly' Users/Patrons, like him) have been able to post in THIS Forum.

    We already know the various mechanisms of providing 'Feedback" that you mentioned; and, that also includes the NEWLY 'revamped' "Communities" in "FamilySearch".

    And, as to 'Support', seriously, have you every actually contacted 'Support' via any means [ie. 'Contact Us' (Telephone); 'Live Chat'(On-Line); and/or, 'Send a Message' (Text), all resulting in a 'Case'] and dealt with some of the "First" (or "Lower") Levels of 'Support'.

    Do not get me wrong, the 'Support' Personnel have always been extremely Polite; and, Engaging; and, as Helpful as they can be, which depends upon their personal experience.

    But, for the experienced User/Patron, with a more complex, less than simple, matter - negotiating your way past the "First" (or "Lower") Levels of 'Support' to get the Case actually considered by those that matter, can be very tiresome and extremely frustrating - that frustration is almost at the level that is implied here in this post.

    Seriously, your response, although I am certain, posted with sincere and good intent, was a little (I should say, 'very much') belittling and condescending, to the many frustrated Users/Patrons (both, Members of the Church; and, non-members) who regularly participate in this Forum.

    Have you taken the time to look through this Forum, of late, over the last 2 years, since you last participated - I am sure you have; and, I am equally certain that you, as I have already indicated, have been very busy and under tremendous pressure.

    'Woody' and We (well, most of us) who regularly participate in the Forum are ALREADY very well aware that the Services available in "FamilySearch" are provided by "The Church of Jesus Christ of Latter-Day Saints" (the Church, for many, Our Church) FREE of Charge.

    You state in your response ... "Our purpose is to "create inspiring experiences that bring joy to all people as they discover, gather, and connect their family -- past, present, and future." ".

    'Yes', remember the old 'catch' phrase ... "FamilySearch" ... "where Generations MEET" ... (I like to add ... "Both, the "Living" and the "Dead" ).

    The most inspiring experience(s) that many of us, 'lowly' Users/Patrons WANT, NEED and DESIRE, is a MORE "Stable" overall Programme of "FamilySearch" (not limited to the subordinate programmes and databases of: "Family Tree"; and, the link between the "Temple" System database; and, "Searching"; and, "Memories"; and, "Indexing") with better "Help" and 'Support - And not to so many UNANNOUNCED "Changes" prior to release.

    Let me say here, from the outset, it is NOT my intention to "Shame", with this diatribe of mine; as, has been suggested in another post.

    I am sorry and apologise, for speaking my mind, for what I believe is the way it is

    It is just so very disappointing to see the such 'limited resources' of "FamilySearch" being SQUANDERED on such as things like the "Family Tree and Friends, Associates, and Neighbor (FAN) Relationships" and the like, when there are MORE IMPORTANT 'competing priorities' that have been requested for some time.

    It has been proffered previously in this Forum, that far too much effort and 'limited resources' of "FamilySearch" is being spent of the many "Campaigns"; and, 'Bells and Whistles'.

    "FamilySearch" has to get back to the 'Nuts and Bolts'; and, the already (too) many 'competing priorities', in "Family Tree" of "FamilySearch".
    eg.
    • Couple Relationships
    • Stop up-load of GEDCOM Files into "Family Tree"
    • Labels
    • "Possible" Duplicates
    • Temple Work Features
    • Linking/Connecting directly with Other "Living" Users/Patrons (ie. Immediate "Family")
    to list just a few.

    "FamilySearch" may be working on these many 'competing priorities'; but, "FamilySearch" could certainly divert those working on all these "Campaigns"; and, 'Bells and Whistles', towards the many 'competing priorities', in "Family Tree" of "FamilySearch".

    "FamilySearch" is spending too much, trying to get "PARTICIPATION" (especially, from Members) with all these "Campaigns"; and, "Bells and Whistles", just like the matter of "QUANTITY" over "QUALITY", that has been raised in this Forum.

    A problem/issue with "FamilySearch", we all know, is "Communications"; especially, the lack of "Communications" when it comes to advance warning for forthcoming "Changes" to "Existing" Features.

    Such lack of "Communications"; especially, when it comes to advance warning for forthcoming "Changes" to "Existing" Features, is certainly a SERIOUS matter for those "Helping"; and/or, "Teaching"; and/or, "Staff" at "Family History Centres"; and/or, "Temple and Family History Consultants".

    'Yes', we can and must (and do) adapt; but, it is not easy when a "Change" has been made that we have not been advised of and are not aware of; especially, when you are in the middle of assisting another User/Patron; and, you have to "scramble" to get you 'feet' again.

    This frustration is NOT directed go the "Engineers" (ie. "Programmers") of "FamilySearch".

    There is some degree of this frustration directed towards the "Designers" and "Developers", I often wonder how many of the the NEW Younger "Designers" and "Developers" are actively engaged in Genealogy / "Family History and Temple Work.

    There is a greater degree of this frustration directed towards the Management of "FamilySearch" who seem to be intent on not only "PARTICIPATION"; but, also, to the detriment of "Family Tree" and "FamilySearch, "QUANTITY" over "QUALITY". And, the lack of an available 'On-Line' record that is actively up-dated with the status of the on-going 'competing priorities' list; and, as importantly available for all Users/Patrons to be able to access and see. Plus, the lack of a personal and direct response or comment from Management (not just the very helpful 'Representatives') to, what we Users/Patrons, consider as as pressing problems/issues.

    Again, this response of mine is not principally directed towards you or your response; but, more a "Cry" for more direct engagement in this Forum by the Management of "FamilySearch", not just the very helpful 'Representatives', like yourself.

    Please feel fee to pass on this frustration with the other "Engineers" (ie. "Programmers").

    And, you people are doing a super job and great work; and, your efforts are very much appreciated by all of us 'lowly' Users/Patrons.

    Please keep up your great and important work.

    Although we are all very well aware that "Praise" is not required, we are all very well aware that "Praise" is very much appreciated.

    Please accept that, although we may whinge and complain more often than not, our great and heartfelt appreciation is implied - But, 'Yes", we should all "Praise" more than we do, Me, especially.

    'Thank You' so much for your continued participation in this Forum.

    Please, if you get the chance, do not be a stranger to this Forum - your insight is invaluable to us 'lowly' Users/Patrons.

    Hopefully other "Engineers" (ie. "Programmers"), like yourself, may get the opportunity and time to monitor this Forum to gauge the mood; and, 'Yes', frustration, of the us 'lowly' Users/Patrons of "Family Tree" and "FamilySearch".

    I am so sorry for this diatribe of mine, your response (although sincere and with good intent) just hit a raw nerve.

    I am, so sorry; and, apologise, for venting my frustration like this, upon you and your response.

    Again, 'Thank You' for all Your efforts; and, those of your colleagues.

    Again, please keep up all the great and important work.

    Brett
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Woody, Tom, Paul, Brett, and Julie:  Your frustration has come through loud and clear.  I truly want to help. Will each of you please send me your top 3 reproducible issues.  Please send me the steps to reproduce each issue in just a few sentences if possible.  I will follow up on each one and make sure it makes it to the appropriate team and let you know what I find out.  BTW: I cannot become the personal go-between for all our patrons, but I am interested in understanding the issues you are dealing with.

    If this just causes more frustration, I will bail out of this conversation.

    Steve
    • view 2 more comments
    • Steven, I have been fighting a bug for several days. I am saving this thread so when I am feeling up to doing more research I can respond to your request.

      Thank you very much for your response and work on this!!
    • I sent Woody's issues to the manager responsible for Search/Match. I have directed him to this page. He is an active follower of GS. Here are Brian's responses:
      44. I get an email, FS has found a Record Hint. Logging in to FS, there are actually two items. The first is a death certificate of my older brother KC35-D6Q whom I never met, he died as an infant. I attach this to his dossier and to the parents as suggested. The second is a death certificate of his twin, a girl. Why is it suggesting this be attached to the infant boy? The indexers have correctly caught the date and gender of both. Our algorithms to don't currently catch that.

      Brian: Because genders are often wrong in Family Tree or Records we don’t exclude a Hint if the genders don’t match. The thing that pushed this female Hint to a 4-star hint was that the death dates / places exactly match. Not normally the case that both twins are stillborn.

      45. (see #44) The Attach function shows the baby boy, the mom & the dad. Looking very closely toward the bottom there are said to be 4 siblings. There is the word "open" which on investigation is actually a hidden link. Clicking on it shows the 4 siblings, including the baby girl KCJJ-8Z7. But there's no way to steer the attach function to attach the girl's death certificate to her dossier. I am leaving this unattached for a while so you may view it as is. https://www.familysearch.org/ark:/619...

      Brian: I wasn’t able to duplicate this problem.

      46. (see #45) Viewing the record, there is a link to view the image. Opening this, it looks like a digitized microfilm - complete with animation! Just as with a microfilm spool reader, we see many quick glimpses of many images as if we were twirling the crank really fast. This lasts maybe 20 seconds until we reach the correct frame. Why on earth are we using up bits on the internet transferring all these images? It's not like we have server bandwidth to burn (see #1)

      Brian: I’ve never seen the behavior described. I will check with Search UI engineers to see if they’ve seen this.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Steven

    I humbly, 'Thank You' so much for taking the time to respond to our "Frustration".

    Frustration, which I must add is NOT directed to you personally or the Programmers (ie. Engineers).

    We are all very well aware that you CANNOT be our 'personal go-between'.

    The problems/issues are far too varied and complex.

    There are too many 'competing priorities' in "Family Tree" and "FamilySearch"; and, there are too 'limited resources' available within "FamilySearch".

    What I (and possibly others) WANT is for the Senior Management and Leaders of "FamilySearch" to TAKE a more "Active" roll in PARTICIPATING in this "FamilySearch" ("GetSatisfaction") 'Feedback' Forum.

    And, not LEAVE the responding to the "Lower" (NO disrespect intended) Level Managers who seem to be the only "Official 'FamilySearch' Representatives" who participate in this Forum.

    We are very well aware that this Forum is MONITORED by "Official 'FamilySearch' Representatives".

    There are a number of serious problems/issues in "Family Tree" and "FamilySearch" that have been raised in this Forum that have not been responded to by Senior Management and Leaders of "FamilySearch"; or, fixed/addressed.

    Not that this problem/issue is something that a Programmer (ie. Engineer) can fix/address; but, just one of the most serious problems/issues that has been raised in this Forum is a REQUEST ('NO', in fact, a DEMAND) to "Immediately" STOP the ability/functionality of Users/Patrons to "Up-Load" their GEDCOM Files in "Family Tree" of "FamilySearch". This REQUEST/DEMAND seems to have fallen on 'DEAF Ears' as far as the Senior Management and Leaders of "FamilySearch" who it would appear to many who participate in this Forum want "QUANTITY" over "QUALITY".

    There is no requirement to stop the "Up-Load" of GEDCOM Files into the "Genealogies" Section / Part of "FamilySearch", just "Family Tree".

    Again, this Frustration is far too varied and complex for you to get involved in.

    What I (and possibly others) would really appreciate if you pass on the need for other Programmers (ie. Engineers), like yourself, to also at least monitor this Forum and read up on some of the more contentious problems/issues causing such frustration (they are rather self evident by the number of "Likes"(or, more so "Dislikes") and "Responses". There is no requirement for them to participate and reply/respond (in fact, if they do, they would never get any work done). And, I do not know how; but, pass it up the line to the Senior Managers and Leaders of "FamilySearch" that there is an extremely high degree of FRUSTRATION amongst the 'lowly' Users/Patrons of "FamilySearch" (especially with regard to "Family Tree")

    Oh, and, lack of "Communications"; especially, when it comes to advance warning for forthcoming "Changes" to "Existing" Features, is certainly a SERIOUS matter for those "Helping"; and/or, "Teaching"; and/or, "Staff" at "Family History Centres"; and/or, "Temple and Family History Consultants".

    Plus, online 'view only' access for us 'lowly' Users/Patrons to an ongoing and up-dated "List" of the many 'competing priorities' in "Family Tree" and "FamilySearch" that are being fixed/addressed; so that, we can actually see their progress and status, keep tabs on it, so to speak. We do not expect to see estimated implementation dates; but, if we could, that would certainly help.

    Again, I humbly, 'Thank You' so much for taking the time to respond to our "Frustration" - we just needed to "Vent".

    Please keep up your great work.

    'Thank You' for your service.

    May the Lord 'Bless' You in this Great and Important Work.

    Brett

    Always the optimistic pessimist.
    • view 6 more comments
    • I can answer some of this, Brett, from what I've been told in other threads.

      First, there are two ordinances that are not consistently recorded in the Temple Ordinance database: Confirmation and Initiatory.

      That is, in my frustrated experience, where most of the inconsistency in dates vs "proper order" for the ordinances.

      First, Completed was used for those instances where there was no Confirmation or Initiatory ordinance in the database. The old "Book of Remembrance" Family Group Sheets had no place to record the confirmation or initiatory dates.

      Second, I've been told (and this is the frustrating part) that a date always overrides "Completed" in the ordinance display page, regardless of whether the ordinance was a duplicate of the original or not (in most cases, I understand that it was from a duplicate).

      Third, I am not sure that the master temple ordinance database contains all of the ordinance data. The reason is that I was instrumental in completing the proxy ordinances for my Father, and when I looked at the record in FamilySearch a year or two ago, I found the Confirmation and Initiatory were recorded as occurring at a later date -- they were out of order, even though I know I performed them in the correct order. The work was done from the old-style Family Group Sheet, and so it did not contain the dates. The only place they were recorded was in the temple record, which is held in Salt Lake City.

      It took a lot of work to finally convince someone that the original temple records for the ordinances needed to be examined and then brought over into my father's ordinance page. Eventually this happened.

      I am hoping that when the rework is finished with the temple system, that the data recorded on the ordinance pages will be the correct data and that for those periods of time when Confirmation and Initiatory were not included in the database, that we see "Completed" back in those slots, rather than the duplicate ordinance dates.

      But I'm also prepared to accept whatever is presented as long as the ordinances show that they have been completed. The date and temple, being of mortality, is immaterial to the eternal nature of these ordinances.
    • Tom

      'Thank You' for your input; and, especially, your personal experience.

      I am well aware of that which you have explained (being a Member of some years now; and, a regular participant of this Forum for some time now) - I just did not want to raise it here; and, cloud the problem/issue.

      'Yes', if I recall, a lot of the "Temple" Work from the 1980's fell into that boat.

      I am glad you fought to have the "Temple" Work corrected for you Father.

      If the "Temple" Work related to a Member of my immediate Family, I would have done the same.

      But, when the "Temple" Work does not relate to ones immediate Family, one does not fight as hard; especially, when trying to deal with the "Lower" Levels of 'Support' (even when it has been passed on up-the-lined to the appropriate Department - very hard to get passed the "Lower" Levels in those Departments).

      I too am also, reluctantly, prepared to accept whatever is presented as long as the "Ordinances" are displayed/recorded as being "Completed" - that is; as, NOTHING has been done to address/fix the problem/issue, that has been ongoing for years. 'Yes', the 'Date" and 'Temple' are 'Temporal'; and, as such, are immaterial to the eternal nature of these "Ordinances"; but, why can't we get it "Right"; and, present a "Record" that is "Worthy of Acceptance".

      I truly hope that 'Steven' considers (and is able to help with) this "Reproducible"; and, reoccurring, problem/issue that I have presented to him.

      Again, 'Thank You'.

      Brett
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Thank you.  You said:
    1. Immediately stop the uploading of Gedcom files into Genealogies.
    2. Encourage Senior Managers and programmers to monitor the forums.
    3. Provide advance warning of feature changes.
    4. Provide a 'view only' list of competing priorities being planned for resolution.
    So your main issues are not so much with reproducible bugs, but with the incoming flow of erroneous data and having an ongoing communication pipeline.

    I appreciate the response.

    Steve
    • Regarding #2 & #4: I would love to see a better form of 2-way interaction and gathering of patron information. Many FS people read the posts, but do not participate in the discussions. I have started a few internal conversations where we have discussed suggestions about how to provide an improved communication path. I'm still giving this some thought. I have appreciated the suggestions so far. The current written communication is too slow. I find it hard to get the time to communicate the way I truly desire. I still need to do my day job.
    • Regarding #3: FamilySearch engineering has implemented Continuous Delivery. This enables engineers to correct your defects submit the changes, have the changes deployed to a test system, run through automated tests, and released to the public within a matter of minutes. Engineers and testers write the automated tests that are run. This enables nearly 900 releases a day. Major changes and updates can be released into an A/B testing model where only a small percentage of the patrons see the changes until we are confident that the desired functionality has been achieved. If problems are identified, updates are made to the automated tests to prevent issues from being replicated in the future. This allows us to make corrections more quickly. It also enables issues to be introduced to the system. This is very different from the old model where thousands of changes would pile up in a new release and everything was tested before a major release was delivered to the public. Both models have advantages and disadvantages. We much prefer the Continuous Delivery model.It has come through loud and clear that you would like advanced warning of interface changes. Continuous delivery does not inhibit this type of communication. I will be opening internal discussions on how we can do better in this area. I welcome your respectful feedback.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Steven

    Oh, I have had; and, do have, problems/issues with "reproducible bugs".

    My initial response was just a quick, 'Thank You'; and, some non-programming problems/issues to pass on.

    Those problems/issues with "reproducible bugs" are only part of "Bigger" problems/issues.

    I am sure that 'Woody', 'Tom', 'Paul' and 'Julie' many be able to provide you with some "reproducible bugs".

    I just did not want your valuable time to be taken away from your work, you must already have enough to contend with.

    We do really appreciate have the "Ear" of a Programmer (ie. Engineer).

    Again, 'Thank You'.

    Brett
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Can I contribute? My top four grievances, all of which have been reported before, but are unresolved.

    * Correct issues with accepting FSID's.
    FSID's follow a set format. Every place that accepts FSID's should call a single subroutine for validating the FSID that will remove white space and standardize casing.
    https://getsatisfaction.com/familysea...

    * Stop the campaigns. Fix "Recommended Tasks".
    We don't need new campaigns. In the end, half of the hints they provide are documents that are already successfully attached in the manner suggested. And all they do is prove that the "Recommended Tasks" list is not working. Review how these campaigns are able to find documents that Recommended Tasks cannot. Review what the mobile app's "Ancestors With Tasks" is doing, because its finding many more documents than "Recommended Tasks". Fix the search queries within "Recommended Tasks" so it can provide these useful hints. When someone comes up with an idea for a new campaign -- figure out why the queries within "Recommended Tasks" are not already providing that information to the user.
    https://getsatisfaction.com/familysea...

    * Redo the 1870 census.
    All of the other US census records allow users to search down to the county level. Please provide county-level searching of the 1870 US census.
    https://getsatisfaction.com/familysea...

    * Fix the Same Place / Same House bug.
    Same Place / Same House (typically on 1935-dated Residences -- added via the 1940 census) is not a standardized place, and should never be marked as a standardized place. These two entries should *always* be red-flagged as invalid locations.
    https://getsatisfaction.com/familysea...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Steven

    I hope that Woody and Tom will come back here and be more specific about outstanding issues when it comes to bugs. Woody appears to be asserting there are still plenty of them that remain unresolved. Tom has previously compiled lists of them (especially following the major FT update) so perhaps he knows specific ones that remain outstanding.

    The one I was about to report DOES at last seem to have been resolved - i.e. the carrying of a "white space" (I believe the term is) acrooss when copy / pasting an ID; which led to a false "Invalid person" error message.

    Unfortunately, some of the problems being reported in this thread are not really bugs but poor features - that nevertheless do need to be addressed.

    My main gripes are the lack of coordination between your staff and the lack of communication with users when new features (and subsequent bugs) appear in the program.

    (Just look at the thread at https://getsatisfaction.com/familysea.... Now was that really too much trouble to your staff. All it needs now is a quick post - from Bryce or a colleague - to say "Resolved" and Gordon & all those affected will be very happy and grateful!)
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Steven

    You might also find the results enlightening if you type "bug report" in the Search Topics field of this forum.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Thanks.  I'll take a look.  -  Steve
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Steven's title is "Director, Engineering and Program Management at FamilySearch" per LinkedIn.

    In that position he is looking for "reproducible bugs" that he can "follow up on each one and make sure it makes it to the appropriate team and let (us) know what I find out."

    As much as I would like to solve or, at least understand, the issue we have with " an ongoing communication pipeline" and GEDCOM upload, etc. I think we should respect his request and only use this topic for providing that.

    As he responded above:
    "So your main issues are not so much with reproducible bugs, but with the incoming flow of erroneous data and having an ongoing communication pipeline."

    It certainly appears he can do something about bug fixes. I'm sure Tom Huber will specifically respond soon, but in the meantime here's HIS new interface unresaolved 'BUG' post:

    https://getsatisfaction.com/familysea...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Steven, the following are unresolved issues that have existed for a long time. I need to update my list or produce a new list of unresolved issues.

    1. The Couple Relationship (which Ron Tanner often calls "spousal relationship") area needs a lot of work. Besides attaching sources issues, there are only four events that can be selected, all associated only with the actual marriage: Married, Annulment, Common Law Marriage, and Divorce. In some countries, a civil marriage needs to be performed before a couple can be married in a religious ceremony. In many locations the license has to be issued at least a day in advance of the marriage. Other events involving the couple as a couple are marriage announcements, affidavits in applying for a marriage license, remarriage after a divorce, banns (often recognized as the same as a license), prenuptial agreements, and same sex relationships, just to name a few. It has been suggested that these be accommodated in notes, but that does not work well, especially when I use Ancestral Quest, which can accommodate various couple-related events. Trying to pass those events (mostly licenses, but also affidavits) to FamilySearch FamilyTree simply fails because the events are not accommodated in any way. I've suggested in some discussion threads that having a "Custom" (fact or event) option, similar to the way the "Other" section for a person's details page can accommodate custom facts and custom events (at the bottom of the list of "Add Information" options). I have seen nothing but pushback from Ron on expanding this section of the tree, despite calls for taking care of this need.

    2. On a person's details page, the “View” function needs to be separated from the “Edit” function -- We should be able to safely look at the details of any entry without going into edit mode. For those without a backup on their local computer, it is a disaster waiting to happen. This issue was introduced with the new user interface about four months ago.

    3. Number of children should be displayed for all marriages when a person's profile is first opened. As it is, when I open a person's profile page, if there are multiple marriages and children for each marriage, only the number of children show for the first marriage. If I click on the children for the second marriage and then close it, then the number of children show. Use Conrad Ross KCM7-QYJ to see this problem.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Steve

    As advised at https://getsatisfaction.com/familysea... there IS still a bug involving pasting of the ID when using the Copy ID function. Screen shot added here, too:



    Once again had to add a space at end of ID for it to be recognised as valid.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • To follow up on a comment that was made early in the comments:

    Such lack of "Communications"; especially, when it comes to advance warning for forthcoming "Changes" to "Existing" Features, is certainly a SERIOUS matter for those "Helping"; and/or, "Teaching"; and/or, "Staff" at "Family History Centers"; and/or, "Temple and Family History Consultants"

    Like the above mentioning specific bugs I think it would be helpful to FS if you can give specifics on how FS can overcome the communication issues. I have seen this mentioned multiple times but no suggestion on how it can be improved has been suggested. FS have the blogs but I know it's often behind and maybe not detailed enough. How much advanced warning do you think is needed ? I have thought about it myself and I am not sure adding something to the sign in page or a banner "this has changed" is a good way of doing it. Mainly because it would get to messy detailing all the changes, like say the person page that was changed recently. I think any suggestions would be helpful. Maybe another post should be started for just that suggestion, not sure.
    • view 7 more comments
    • Minor changes to wording or phrases (substituting merge for delete, for instance) are fine, but any kind of interface change, such as those recent changes involved with the Research Help area, need to go through some kind of beta testing and feedback.

      Right now, there are several issue in the unresolved issues list that deal more with recent changes in the way the Show All page behaves especially with regard to dismissed helps, the way duplicates hard (not) handled, and so on. A lot of the complaints that now exist could have been avoided with user-involved beta testing.
    • Thanks
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned