Describe the bug
appcues code still exists in the UI even though it is no longer used.

To Reproduce
see PR https://github.com/zesty-io/accounts-ui/pull/119/files for the files that were originally modified to add the appcues code

(created from Zendesk ticket #893)
gz#893

Is your feature request related to a problem? Please describe.
there isn't a method of organizing instances other than favoriting them, giving ones that are like each other a similar name, or ecosystems - which is only useful if your instances share media.

Describe the solution you'd like
It would be great to have a folder system to organize your projects. That would enable users to organize projects that are in-progress, under review, finished, etc. and opens up a new, more flexible way for users to work and be more productive in Zesty.

Describe alternatives you've considered
Some alternatives are described above such as similar names, ecosys for instances that share media

Additional context
this is a customer request - see the zendesk link below.


(created from Zendesk ticket #1257)
gz#1257

Describe the bug
user state including user.ZUID is missing, resulting in missing username/email and My Account information.

To Reproduce
Steps to reproduce the behavior:

1. Login with 2FA
2. See missing username in top-right user menu

Expected behavior
expect User record to be fetched and top right menu with username

Screenshots

Is your feature request related to a problem? Please describe.
Using a very old design system dependency in accounts-ui
https://github.com/zesty-io/accounts-ui/blob/master/package.json#L33

Describe the solution you'd like
update design system dependencies

The accounts signup page should have a Microsoft SSO button, same button as the login page. This doesn't require any backend changes.

Is your feature request related to a problem? Please describe.
We've received user feedback that users are discouraged from starting sandboxes because they don't want to be charged additional per new instance.

Describe the solution you'd like
In the accounts pane, providing a clear visual indicator of production instances vs. sandboxes or dev environments would be ideal. Maybe a green pane at the top with production instances, and the rest in the light blue view below so that there's a clear visual delineation of the difference of active instances vs inactive.

Describe alternatives you've considered
Open to other alternatives.

Additional context
N/A

Describe the bug
When all of PD's instances are sorted alphabetically they do not sort correctly. A portion will go from A-Z, then another portion will start again at A. Note: I first noticed this when looking at PD's ecosystems but it impacts the all-instances view too.

To Reproduce
Steps to reproduce the behavior:

1. Go to Accounts
2. From the EcoSys dropdown select Petdesk
3. Once all instances are displayed ensure that the sort that's selected is A-Z.
4. Scroll down and look at how all instances are sorted.

Expected behavior
Alphabetical sort will sort ALL selected instances alphabetically.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Mac Mojave
• Browser Chrome
• Version 84.0.4147.89 (Official Build) (64-bit)

Smartphone (please complete the following information):
n/a

Additional context
Loom: https://www.loom.com/share/3c403df6584245ef89d8771af5500f06

Describe the bug
In the instance list view when changing from instance A overview to instance B overview the app crashes.

To Reproduce

1. Go to instance list view
2. Click on instance A overview
3. Click on instance B overview
4. See error

Expected behavior
Changing instances overviews loads the instance details.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Ubuntu
• Browser: Chrome

The instance filter(search) should return results when entering a ZUID or hash.

• t0sxcdwl should show alphaunviverse
• 8355045 Hofbrahaus

Describe the bug
Favorited instances are not saved between sessions.

To Reproduce
Steps to reproduce the behavior:

1. In Accounts - add a star to the instance card to favorite it.
2. Sign out of Zesty
3. Sign in to Zesty
4. See that your favorites have not been saved

Expected behavior
Favorites will be saved between users' sessions.

Screenshots
Shows console error:

Desktop (please complete the following information):

• OS: Mac Mojave
• Browser Chrome
• Version 84.0.4147.135 (Official Build) (64-bit)

Smartphone (please complete the following information):

n/a

Additional context
Add any other context about the problem here.
Here's a Loom: https://www.loom.com/share/b8debf4236944875ac4e2a19f1e08706

@grantglidewell looks like with the most recent password change flow fixes it's broken the cypress test. Can you take a look when you have a moment?

p.s. I've tested manually and everything is work so will be shipping this to prod.

Need to add build information in JSON format as a route in the app / or a static file. Useful to know what's currently deployed.

Login Accounts => Select My Accounts => Blue Print modal needs to be removed.

Describe the bug
Editing an instance name allows for addition of leading and trailing whitespace

To Reproduce
Steps to reproduce the behavior:

1. Go to instance overview
2. Hover instance name
3. Click on pencil icon
4. Edit name to include white space
5. Click save

Expected behavior
We should trim white space from instance names on user input

Screenshots

Additional context
We should also be trimming white space during instance creation when naming the instance

Is your feature request related to a problem? Please describe.
To support a simple app registration as part of the new marketplace we need to build a UI which allows the registration of custom applications.

Describe the solution you'd like

Describe alternatives you've considered

Additional context
Once completed we should update the app guide registration readme.

This is especially confusing with the issue #136 as you have no idea on which domain this delete action is occurring.

Is your feature request related to a problem? Please describe.
Not all users understand that when they enter a custom domain it should be limited to the root without a trailing slash or protocol.

Describe the solution you'd like
I would like a tooltip or placeholder text instructing users on what needs to be entered such as: enter domain without trailing slash and protocol for example: example.com

Describe alternatives you've considered
I've updated the documentation with these instructions, however the instance settings drawer launch instructions are made to empower a user to launch their site without using the docs so I don't know how many users use them.

Additional context
Add any other context or screenshots about the feature request here.


(created from Zendesk ticket #1277)
gz#1277

Describe the bug
A customer recently asked if we could change the name of their instance. I explained that they could change it themselves by clicking on the name in the instance settings drawer, however there is no indication of it in the UI.

To Reproduce
Steps to reproduce the behavior:

1. Go to the Accounts UI and view the instance settings drawer
2. See that there is no visual indication that a user can change the instances name

Expected behavior
There should be some kind of visual clue that the user can click on the instance name in the setting drawer to change it.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Mac Catalina
• Browser Chrome
• Version 85.0.4183.121 (Official Build) (64-bit)

Smartphone (please complete the following information):

n/a

Additional context

Is your feature request related to a problem? Please describe.
When a user launches a site step 1 asks them to enter a domain, however there is no instruction/indication for what the dropdown does and it allows users to add a domain without selecting a branch.

Describe the solution you'd like
Instead of -None- it would be helpful to instruct the user to Select a Branch & not allow the user to click the 'add domain' button unless a branch has been selected.

Describe alternatives you've considered
Add a note to documentation explaining what the dropdown is used for. However, I know that not all users will look at the documentation therefore it would be better to have that instruction in the UI (in addition to the docs).

Additional context
side note: I think the spacing in the dropdown could be tightened too.

Is your feature request related to a problem? Please describe.
Currently we show a generic message on basic auth failure. This creates confusion on the error that occured.

Describe the solution you'd like
We should display the error message returned from the auth service. see screenshot.

• the empty token name & role experience should be clearer. Show an error explaining they are required. Do not open modal.
• Node SDK should be using the url component to get consistent styling.
• Token should be selectable text to allow for manual copying. Pasteboard functionality can be inconsistent across OS & Browsers. Relying on that is not good.
• Delete token button should be styled as a red delete button. See how domains is doing it.
• Create token button is extending past the card padding. Makes the layout inconsistent in comparison to other cards
• atom IDE text should link to https://zesty.org/tools/atom-package

Describe the bug
Inside instance settings drawer under Set Your Domain of the publish your instance box -- the add domain button is unavailable when domain is formatted correctly. However when the domain to be added is formatted incorrectly and includes protocols the add domain button becomes available.

Expected behavior
without protocols the button should be available.

Screenshots
Testing Video:
https://www.loom.com/share/36d1678c78df4fae82954ab4f4eb1ba5

Describe the bug
Toggle Manage Teams in My Account Preference section does not work.

To Reproduce
Accounts-ui > My Accounts > Preference section select Manage Teams toggle > will get a notification saying successful but it will not toggle over even on refresh.

Expected behavior
Toggle to green should light up

Screenshots

Is your feature request related to a problem? Please describe.
The accounts-api is providing a new endpoint for instance creation and population. We need to update the UI to use this new endpoint and tweak the experience to match new expectations.

Describe the solution you'd like
The new endpoint docs describe how formulate the request. Because this endpoint is handling population, formerly this occurred in site-manager-app on a different URL, we will need to add a new loading experience between blueprint selection and redirecting to the instance settings overview. This is to communicate users should wait will the instance population occurs. This loading screen should use the WithLoader component from the design system.

Describe alternatives you've considered

Additional context

The domain card should always be shown.

Both the Domain and Access token tables when containing multiple rows are having the actions affect a different row.

Issue

e.g. When there is more than one domain listed. The delete domain action removes the wrong domain.

Expectation

Actions on a row only effect the values of that row.

Solution

This is highly likely due to the way rows are being generated and what is being used as the lookup reference value when the action is taken. This should be using a ZUID reference not an array index.

Describe the bug
Users are reporting the Accounts UI not loading and getting stuck with the message "Finding Your Account"

To Reproduce
Steps to reproduce the behavior:

1. Go to accounts.zesty.io
2. See that the UI is stuck without loading instances or login screen.

Expected behavior
Expect a instances to load or login module to display when loading accounts.zesty.io

Screenshots

Sensitive client information. Zesty staff access only. See internal note in Zendesk for screen capture: https://zestysupport.zendesk.com/agent/tickets/1121

Desktop (please complete the following information):

• OS: MacOS
• Browser: Chrome

Additional context
I have not been able to recreate this on my end but have multiple reports from client about the occurrence. See internal note on Zendesk for screen capture.

Describe the bug
when clicking the live link from the instance card the link always sends the user to https. This causes sites to err out when they're not on https and confuses users.

To Reproduce
Steps to reproduce the behavior:

1. Go to an instance that you know is using http
2. Hover on the globe icon
3. See the link that is going to https
4. opt: click the globe icon to see the site err

Expected behavior
The globe icon should respect instance's protocol

Screenshots

Desktop (please complete the following information):

• OS: Mac
• Browser Chrome
• Version 87

Describe the bug
On the grid list view when a user was previously a member of an instance and they had favorited the instance if they are then removed and re-invited to an instance the pending invite card will not be shown unless the instance is un-favorited
To Reproduce
Steps to reproduce the behavior:

1. Invite user to instance
2. Accept invite
3. Click "favorite" instance stare
4. Remove user from the instance
5. Re-invite user from the instance
6. reload accounts
7. see pending invite card is missing but favorited instance (which user no longer has access to) card is shown
8. un-favorite instance by click star
9. see pending invite now shown

Expected behavior
Pending invite cards should be shown regardless of whether the instance had previously been favorited

Screenshots

Additional context
When a user is removed from an instance we should probably remove the favorited status of that instance from their preferences

Please swap out *.preview.zesty.io references with *.webengine.zesty.io

Describe the bug
The link to an instances settings from the instance overview links to legacy site-manager-app. This needs to be updated to point to the manager-ui URL for that instances settings.

Describe the bug
Team members cannot be individually invited to access an instance if the role has more privileges than the Team's role.
eg if a Team has the role 'developer' an individual user, who is also a team member, cannot be invited with the Admin role.

To Reproduce
Steps to reproduce the behavior:

1. Add a team to an instance with a role Developer
2. Invite one of the team members to access the instance with an Admin role - see invite fail.

Expected behavior
Individual roles take priority over the Team member role - even when inviting individual members to access an instance.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Mac
• Browser Chrome
• Version 89

Additional context
Add any other context about the problem here.

Describe the bug
Link still going to legacy site-manager-app

Expected behavior
Update link to go to manager-ui

Screenshots
If applicable, add screenshots to help explain your problem.

Describe the bug
In Dev environment, clicking Sign Out results in 404

To Reproduce
Steps to reproduce the behavior:

1. Logged in
2. Click on 'Sign Out'
3. See 404

Expected behavior
Goes to /logout, then redirects to /login

Screenshots

Describe the bug
Enabling 2FA with a primary phone number and no country code responds with Two-Factor auth had a problem enabling

To Reproduce

1. Login into an account that doesn't have 2FA enabled
2. Navigate to account settings
3. Enter phone number into Two-Factor Authentication (2FA) section(leaving out the country code) and click ENABLE AUTHY 2FA
4. See error

Expected behavior
Send PUT to Accounts API only when BOTH phone number and country code are present. Responding with Two-Factor auth enabled

Additional context

• PUT to Accounts API is returning a 400 status code with error message:

Bad Request: failed to enable authy: request to register authy user failed with status code: 400

• The Request Body's authyPhoneCountryCode key should have a non-empty string value.

Is your feature request related to a problem? Please describe.
If a user has created an account using SSO, then 2FA and password reset is not necessary.

Describe the solution you'd like
Remove 2FA card and Password card in accounts.zesty.io/settings/account

Describe the bug
Logging in with 2FA enabled has missing user information.

To Reproduce

1. Login into an account that has 2FA enabled
2. Navigate to account settings
3. See error

Expected behavior
User information is populated using the return of GET {accounts_api_url}/v1/users/:user_zuid.

Screenshots

Account Settings:

Additional context
See non-2FA login for expected behavior.

Is your feature request related to a problem? Please describe.
We have a new signup experience at https://start.zesty.io. This will be the primary flow going forward. Making the existing accounts UI signup for legacy.

Describe the solution you'd like
Switch account creation links to https://start.zesty.io.

The legacy sign up form should remain in accounts-ui and the link used for invitation flows. That is when a user gets invited to an existing solution they should not go through the start.zesty.io flow and create a new instance.

Additional context
To accomplish this we need to consider the other flows around accounts and if this has an effect on them

• instance invites
• team invites
• password reset
• email verification re-send

Describe the bug
Legacy Manager button takes 100% width. When trying to click the close button and if slightly off it will fire off the Legacy Manager button.

1. Go to https://accounts.zesty.io/instances/8-84ccb1acd5-kl5cj8
   Highlight anywhere to the right of Legacy Manager button and mouse pointer will turn on.

Expected behavior
Should be clickable of button width only

Screenshots

With the recent update to domain management allowing for multiple domains we need to update how the "Production Site" link is determine. This also affects sites repo which show live links to content.

Issue

Currently we have instance which are using "dev" domains for the live site link.

The "globe" icon links to the sites domain.

Solution

Filter production link to only show those which point to a "live" branch.

@hectorsanchezmx switching instances can still trigger an app crash.

We need to ensure the domain props is always an Array. I'm consistently seeing this in the list view when I have one instance open and then switch to another.

On larger screens the column values don't line up to the column headers.

Describe the bug
After an team invite has been accepted when the UI is reloaded it will continue to show the team invite acceptance card incorrectly.

To Reproduce
Steps to reproduce the behavior:

1. Create a team with account A
2. Invite account B to the team
3. Login with account B
4. Go to teams tab https://stage-accounts.zesty.io/teams
5. Accept team invite
6. Reload browser tab
7. Team invite is re-shown incorrectly

Expected behavior
After a team invite is accepted the invite acceptance card should not be shown on return visits

Screenshots
If applicable, add screenshots to help explain your problem.

Click accept invite showed error notification

Desktop (please complete the following information):

• OS: Ubuntu
• Browser Chrome

Describe the bug
When you click the settings to edit a team's info...I am not able to edit any info.

To Reproduce
https://www.loom.com/share/a8c6ad21fd96459fab000c23ec61ebf6

The 2FA code entry form offers a list of previously entered values for this field. This form field should be made exempt from autofilling.

See attached screenshot.

Business request to hide the link Sign Up free link on the sign in page

https://www.loom.com/share/61427bcba2914cadb15dcdd224ac2a4d

pw: zesty

Describe the bug
When creating a new Instance if you click the Eco Dropdown and Selecting None you get a creation error because it tries to 0 as an arg. invalid or unknown ZUID (0) provided for ecosystem

To Reproduce
Steps to reproduce the behavior:

1. login to accounts
2. Click on create instance
3. click the Eco Dropdown and Select None
4. enter instance name
5. click create

Expected behavior
should not error and create an instance