I think this is related to the timing of the batch job to do the reindexing vs when new data is uploaded and there is a created delta.    I am not sure if there is something that can be done to correct this considering we are expecting a revised site (based on different technology) in the coming months, but I will check. 

Even after more than 1 week since release, patches F214/G414 are not mentioned in the "reported issues". Perhaps something went wrong in the patches rollout procedure. Happy Easter, Uli

Thanks Uli, I've asked somebody to take a look. Not sure why we seem to have had some issues recently, but we'll work on getting things reliable. 

Hi Adrian, thanks for the fast response. For "old" uniface experts like me, the KBL ("known bug list") is still the center of all kind of very important information. One of it is "when I experience this problem, is there any patch to fix the problem?". This is one of the reasons why I have my sunday routine to query the KBL to get an updated status. Best wishes from Frankfurt/Germany to all the nice people in Amsterdam, Uli

Just to make the error reported complete: Patches above G320 are not shown as well.

Uli, can you check something for me, and if there is still an issue, give some step by step instructions on what you are doing and what you are expecting?  I thought I experienced issues with the results also, but I think what I discovered is actually a usability issue (which I've asked to be looked into).  My use case: 

From here: https://unifaceinfo.com/fixes/patchlist/patches9704.php

 

I see the most current patch is G402.

 

From the bug 31270 I copy ‘HTML widget’    

 

I go to: https://unifaceinfo.com/reported-issues/

 

And paste in HTML widget 

 

Bug 31270 doesn’t come back in the search.

 

But searching 31270 does return the bug..

 

Hi Adrian. 1) I open the "Reported Issues" query 2) I enter some profile like "SOAP" and got some hits 3) among them, Issue 31568 with the text: 31568 BUG: 31568 - SOAP security update Status: Planned for resolution in 10.3.01 Patch(es): F115 G315 Symptoms: SOAP security update - So I immediately see in a central place that there are patches to cure the bug and which one I have to install to fix the problem   AFAIK, this information is delivered by uniface since the early 90's and still used by a couple of experts. Greetings from Frankfurt/Germany, Uli   P.S. Sure, one can compile this info from some other sources, but the combination is a much better support for the community.

Hi Adrian, Could I add another use case? When a search reports many occurrences it would be nice to have an option to order them from older to newer or from newer to older. Regards, Gianni

Hi to all "Known Bug List" users: today, I found that the patches info on Issues is updated up to the recent F212/G412. This is pretty helpful to detect if this is an "open issue",so we have to wait or what patch has to be applied. Thanks for this effort and keep on the good work, from an ice-cold Frankfurt/Germany (-6° plus windchill), Uli P.S. And a big THANKS for implementing Gianni's wish for the sorting order.

Well, patch F213/G413 hasn't made it to the KBL even if issue 31620 is shown in https://unifaceinfo.com/fixes/patchlist/patches10202.php Sorry to say, one can not trust the KBL as one could do all those decades before.

Hi Unifacers, searching for the word "issue" I am expecting to find all issues ordered as requested from the front-end, by default from newer to older. It works, however a couple of issues are always shown at the beginning, I suppose because a release date is missing or is into the future; they are 7 in total and these are their addresses: - https://unifaceinfo.com/fixes/patchlist/patches9604.php - https://unifaceinfo.com/fixes/patchlist/patches9603.php - https://unifaceinfo.com/fixes/patchlist/patches9501.php - https://unifaceinfo.com/fixes/patchlist/patches9401.php - https://unifaceinfo.com/fixes/patchlist/patches9203.php - https://unifaceinfo.com/fixes/patchlist/patches9202.php - https://unifaceinfo.com/fixes/issues3.php Could this small data bug be fixed? Thanks! Gianni

Hi Gianni, it looks like all your references point to COLLECTIONS of issues, not single ones. One may discuss if these should be returned in a query of reported issues.