## New Features
-  We now support Compliance Elasticsearch Migrations, both from Automate 1-to-Automate 2 and Automate 2-to-Automate 2. Our Beta customers can keep their data when upgrading to the latest Automate 2.  Remember, a migration begins with the current day--today--and then works backward in time to the very first record. While the current day--today--migrates, it blocks both ingestion and the UI, which makes the app look like it is taking a long time to start. A migration usually takes only a few minutes, but on larger systems--such as those with 150k nodes--a migration may take as long as 10 minutes. Migrations take place quietly and in the background.  During the historical compliance data migration, the compliance service remains available for viewing and ingests new reports as usual. Migrations happen automatically at the compliance service start-up.

## Improvements
- Improved Compliance Profile Store: Install market profiles to your namespace faster. All market profiles included in Automate 2 are Inspec 2 compatible.
- Improved Compliance Reporting UI: Use a simpler single-date-picker in the search bar and adjust the trend graph to show the last ten days, month, three months, or year.

## Bug Fixes
- Delete user session on logout.
- Fix Node Run Summary view shows run ID instead of the node ID. 
- Define or specify users with _username_ instead of _email_ in the users API.
- Users in different timezones, meaning across UTCs, can view all the reports because we now account for differences in user's times as well as their dates.
- Legacy profile routes used by audit cookbook for fetching profiles have been exposed in A2, meaning you should now be able to refer to your installed A2 profiles when using the audit cookbook.