Changes were applied to improve security. See ADV-2019-001, 2019-002 in Security Bulletins for more details.
UPN prefix longer than 20 characters imports username with sAMAccountName, not UPN prefix as expected.
After upgrading some nodes in a cluster to 2018.2, navigating to the Extensions tab resulted in an "An unexpected error occurred while processing your request. Try again. Undefined" error
Sometimes, the checkbox for "Permanently convert from fixed schedules created by administrators to custom schedules created by users" would not save.
When connected to SAP HANA with a LOD calculation on Filters, dragging any dimension not included in the LOD to the view returned a "Bad request: The data source does not contain the expected data. No such column" error.
When interacting with filters, an intermittent "tuple id cannot be resolved" error occurred.
Guests could not access a workbook published to a non-default site unless guest access was also enabled for the server's default site.
Gridlines did not render in a dual axis view with a reference band.
Images in published vizzes intermittently failed to display.
When Tableau Server was configured with SSL for internal Postgres communication and site-specific SAML, server-wide and site-specific SAML authentication would both fail.
Publishing an extract sometimes resulted in an "Invalid extractUpdateTime specified" error when region was set to Thai.
After running a subscription on a public custom view, the dashboard sometimes showed incorrect numbers.
In a Tableau Server 2018.2 or 2018.3 deployment on Windows Server 2016 some management services including tabadmincontroller and tabadminagent may not automatically start up after a system reboot, requiring the user to bring up these services manually before being able to manage Tableau Server.