This same BUG existed in TurboTax 2018 and now again in 2019. This is horrible programming and support for a know BUG that has existed for many years. Has anyone found a work around to this issue?
