Hello again everyone, I've been working with our internal teams on this some more, as we've seen more feedback roll in on this. We're re-evaluating the scope of this issue, and will be investigating if there is an opportunity for us to provide a fix prior to 2019.1. I can't promise anything at this point in time, but thanks to everyone that has reached out to us, this is back on our radar. If you haven't already, please submit a ticket to support, and we can keep you up to date as we hear information there. Thank you all again, your feedback has been tantamount to us addressing this issue. Dustin Martin Assigned Support Engineer Workfront