It appears that this bug is not present in the final update of 2018 TurboTax (R48) but was present in the first release of 2019 TurboTax (R4) and is still present in the current release (R12).
