A fairly simple case. We made a design error at the start treating jobs as separate entities, when in reality the will be grouped and generally flow together.

A fairly simple case. We made a design error at the start treating jobs as separate entities, when in reality the will be grouped and generally flow together. (Jobs in a production context are various objects made with the same set of specs. Jobs in a customer context often include some objects that are fancier than others.) We took the lazy route and provided a means of linking jobs to a parent. I tweaked the weighting somewhat because some changes were more likely to be related than others and displayed the top 20 choices. The next step was going to be an input box to let the user pick--but it didn't get written because the desired job always showed up. That state persisted for years before it finally didn't cough up the desired job in the top 20 list. Looking over the problem case they had done something with the name that hadn't originally been envisioned that caused it to score badly--but even then it turned out to be in slot 21. Someday it will need an input box but the quick fix was to simply add another menu option to the list.