WHAT:
updated overview step of onboarding tour. It shows upload data methods instead of tour steps now
WHY:
new onboarding tour
Change-Id: I7ffe9b2b91c2e17dd0c27e5e80a15301f6de16aa
WHAT:
first step of updating onboarding tour - adding routes
WHY:
onboarding your is being reworked so adding routes will make it easier to operate over it's states
Change-Id: Ide830989e39a6222e975bd2a6106b0efbb3839f9
WHAT:
search for bucket names during creating access grant flow
WHY:
make user be able to search for needed buckets. Just in case if the number of buckets is too large.
Change-Id: I73bcaa160c7a1f433d8f0f7213999e7e40543bbc
WHAT:
enter passphrase step for create access grant flow
WHY:
if user already has access grant, passphrase could be used one more time
Change-Id: I7ceb6ca5b59a1d72510c739e268c73c511bbedef
WHAT:
create passphrase step for access grant flow
WHY:
passphare is needed to generate access grant
Change-Id: I9d0540826744d192b2e00a30fda907cc581a6e00
WHAT:
continue in CLI step which returns regular API key
WHY:
in case user wants to create access grants in CLI
Change-Id: I8a0fa15f07e553628bda3a3e871506295230f0a2
WHAT:
bucket names selection logic for create access grant flow
WHY:
bucket based access grant restriction
Change-Id: I922811ce43afbc0bf0c2c9bcaea755657257f26f
WHAT:
permissions step page for create access grant flow. Regular permissions and buckets dropdown
WHY:
to configure access grant permissions
Change-Id: Ia5571556a7fb83fd9a508e6aabfcdf5b57e9bc96
WHAT:
progress bar for create access grant flow
WHY:
progress bar to show user current step of the flow
Change-Id: Ia3665fee91ac9b3c27eed5d5190e69d7ea5b3e8a
WHAT:
access grants list page where all the created access grants will be visible/deletable
WHY:
initial page of new access grant flow
Change-Id: I0b99f15e47295bd0d307dd3aebd9f6dea3ffbb25
WHAT:
Now project amount limit is taken from users db instead of config. But if db value is 0 then default config value will be used instead.
WHY:
this will allow us to change user's project limit by changing db value.
Change-Id: I9edcd0bf9eaae5fe40e90a44cac82d9ce8519274
WHAT:
new project summary (details) section added to project dashboard page.
v1 shows team size, API keys amount, buckets amount, estimated charges for selected project for current month.
WHY:
redesign. Better user experience?
Change-Id: I31204a3e68db49486bad1e1a0eedd238eba6b84e
WHAT:
working logic of dropdowns moved to local store. Removed ability to open more than one dropdown. Dropdowns' colors changed to satisfy needed contrast ratio
WHY:
better user experience
Change-Id: Ia7a5683a3544fcb6bdd8a05d1fd6a12755b76caf
WHAT:
in case when user was in no paywall cohourt, unnecessary error message appeared in console after login.
Error removed.
WHY:
better user experience.
Change-Id: Ieafd756e3dc0d6a10bf0058b52ebfaf38d02e8fd
WHAT:
lastly selected project is now stored in browser's local storage and is being selected automatically on data load (login/refresh)
WHY:
better user experience for multiproject state
Change-Id: Idadbb75c8391017ee1845415bec282d9e33309eb
WHAT:
added functionality for user to update project name. Logic only, without actual GUI updates.
WHY:
better user experience
Change-Id: I1e38e33ba827b0bdf2c89e29de24e4e87edb474a
WHAT:
Navigation sidebar reworked.
Project dropdown moved back to header, resources and settings sections moved to header as dropdowns.
Header reworked to match new design.
WHY:
GUI redesign
Change-Id: I73e1269326d3dbfba2e44d848dba4a415e64e539
WHAT:
notification bar added to project dashboard page. It is shown when projects count limit is reached.
Create project button is removed after creating last available project
WHY:
inform user that their projects count limit was reached
Change-Id: If0d67148003be40cc9eb4d8b25cc17f8204008d4
WHAT:
dashboard and billing pages' scrolling fixed with no paywall banner
WHY:
content was slightly clipped
Change-Id: I4d663775456980887af7bc41c72bf3a8da87d301
WHAT:
info bars for accounts with no paywall implemented, USR-976
WHY:
we should notify users with no paywall that available coupon value is running low or coupon is used
Change-Id: I1a84afce890515b3aaedf1f0b8d359499af05471
WHAT:
yellow low balance banner removed from billing page for no paywall users
WHY:
better user experience for no paywall users
Change-Id: I1c254d7696e166073c66a6fbb82c134903cbc920
WHAT:
modal with saving API key confirmation implemented for onboarding tour
WHY:
ensure user saved API key
Change-Id: I9bc000cf5a19a9d6fc9eb3a4bfb9156d6b4bc78f
Add a config so that some percent of users require credit cards /
account balances
in order to create a project or have a promotional coupon applied
UI was updated to match needed paywall status
At this point we decided not to use a field to store if a user is in an
A/B
test, and instead just use math to see if they're in a test. We decided
to use MD5 (because its in Postgres too) and User UUID for that math.
Change-Id: I0fcd80707dc29afc668632d078e1b5a7a24f3bb3
WHAT:
completed transaction state condition depends only on stripe balance now
WHY:
avoid waiting for transaction status to update
Change-Id: I09be620f94934209b60ef692ffcc0f5097880920
