I have reported several notation problems to PGMusic, and always seem to get the same answer "We've reported all three issues to the developers for their consideration."

Here are my issues
Section Text using the “T” button on the notation screen
Text above / below the staff can be entered correctly including tick based horizontal and vertical positioning, but when printed in Fakesheet mode the
text designated for the first beat of a bar is printed hard left rather than horizontally shifted as required. If printing in ‘non-fakesheet’ positions
the text in the correct place.
This worked in the past - I have song printouts for the same song from 2014 which prints correctly

Part Marker on 2 bar ending
A part marker is now automatically created when using a 2 bar ending which starts early.
You are able to cycle through the 3 parts (A, B or no part marker) but it does not ‘stick and reverts to A marker as soon as you leave the notation page.
This auto part marker also creates a double bar line which is unnecessary and confusing. Problem exist in both Fake and non-fake printing.
It is fairly new, as I have prints from 2014 which do not show double barline

DS al Coda ‘missing’ after repeat.
The sign, the end DS phrase, and the start of the coda are present. The actual DS al coda designation is lost under the repeat sign.
This problem has existed from the first implementation of fake sheet. Combination of repeats and DS are used when you only want a short piece of the verse
repeated as an ending, for instance

Lyric Shifting
Note lyrics on the first beat of a bar are shifted hard left which often makes the lyric text unprintable / unreadable on the first bar of a staff.
I suspect this began with the introduction of bar based lyric and the quick entry feature and is related to the text entry problem

I have had some strange responses from PGMusic for the reasons for these bugs but "Repeats, codas, and endings have always been a difficult feature to program in Band-in-a-Box due to the algorithms used to generate the RealTracks" seems to be a stretch. They seem to be blaming code that has never worked on Real Tracks, even before real tracks existed.

I have developed some work arounds, but they should be not be required.

BIAB for Windows Version 2019 (643)
Windows 10 (1909)