Not sure what caused this but the lead table doesn't sort anymore when you click on the headers.

Logging out on our application causes the Google account to be signed out across all google applications.
Additionally, on the chrome book, logging out pulls up the account management settings page for the device (as it seems like it is prompting for a complete log out of the account from the device), which is not a feature we want.

Additionally, when logging in while already authenticated, if it is possible, we probably want to allow the user to choose which account or have that additional confirmation page instead of instantly taking them from landing -> guide.
Instead, it should look like landing -> choose a google account -> guide.

Accessing a page that needs authorization (i.e. crm/leads or crm/forms) while not logged in just keeps the leads table loading infinitely (since the server denies the request with 401 Unauthorized).
Expected behavior would be to redirect to the landing page.

Right now, we are creating our own filter predicate function in . Our method currently involves traversing each lead's JSON and appending all the values together in an accumulator and then checking if the filter string is a substring of this accumulator.

For example, consider a user filtering for "template" on this sample json:

{
  "a": "temp", 
  "b": "late" 
}

Our filter predicate would include this in the filtered results because the filter string "template" is a substring of the concatenation of the values ("temp" + "late").

What we want to do instead is check if "template" is a substring of each value individually.

Ideally, I would like to create an E2E test for lead creation process i.e. from logging in to posting lead to seeing form table and lead table populated.

Landing page doesn't style correctly for some reason (maybe associated with the JS error).

Additionally, the login button doesn't show text sometimes and when clicking it, it sends to /undefined -> seems like an error is happening in the login service.

Believe these bugs are associated with the recent i18n changes.

Only a certain part of the sidenav buttons are clickable. We probably want the entire button to be clickable.
Same happens when the side nav is hidden and only the icons are shown.
https://screenshot.googleplex.com/j73KOKEcawW.png

These classes are nearly identical and mostly consist of an id and name where the name can be changed.

Production datastore needs a index to prepare the query before hand.
Should be a simple fix by supplying an index.yaml file through the gcloud CLI.