I have recently upgraded from V5.1.3 to V6.0.5-1. Previously I ran the Complete Individual Report and it sorted the people in Alpha order based on surname. When I run Complete Individual Report in V6 it does not sort the people in any order I can work out. Is there a bug with this report as I cannot find anywhere on how the report is sorted. On ‘Report Option (2) I use Name Format ‘Surname, Given Suffix’ but the first person on the report is ‘Strutt, Thomas’ and he has an ID of I004042, the next one is ‘Anstead, William I000874’, next is ‘Ablett, Henry I005713’ so as you can see no sort of order.
By the way, I maintain a “private” placeholder person with a log “ToDo” Note of my patches to Gramps. It includes hotlists to discussions about the “why” of those patches.
This gives me a checklist of changes to apply to newly installed updates. And, as a dummy/placeholder Person, it travels with my Tree backups.
@emyoulation The script change that was in the previous post sorted based on the Date of Birth and had issues with those that were “Estimated”, “Before”, “About” and “After”. The script looked normal in the Version 5.3 I was using so not sure why it worked in 5.3 and not in 6.
What is involved with “adopting” the report patch as I don’t understand any of the coding and also the patch I used didn’t do what I wanted it to.
Further to the above. If I run the report and then close GRAMPS, reopen and run the report (with exactly the same settings), close GRAMPS, etc , the reports are in different order, ie
Report 1 - MacKenzie, (Unknown), Clarke
Report 2 - Gordon, (Unknown) [but different Unknown], Seller
By “adopting”, I mean that you use your “les.61” account on MantisBT to comment on the Bug report. (Noting that this Discourse thread has a patch related to that issue and linking this thread would be a good comment.) The comment will make MantisBT notify you if there is any activity on that issue.
Then try any patches proposed just as you did before/above. Giving feedback about how well they work or do not work.
Then, when the next public Beta test starts, make certain we are reminded if that issue solution is not part of the release. And verify it still works if it IS part of the release.
Basically, become the main bug tester for this issue.