Next

Related to #1582

changed milestone to %sprint: Jolly Jellyfish

added MR::Awaiting Review Priority::2 - Normal Product::Wallet Squad::Blue Type::Feature scoped labels

Could do with a second opinion on wording of the notifications.

added 1 commit

• ab0ae00b - (feat) Display token multiplier on contributions page and apply to the...

Compare with previous version

added 2 commits

• 7ea80d90 - (feat) Rewording of daily reward notification to indicate tokens were earned...
• 378e5453 - (fix) Regression in chart component test due to requiring input values - #1488

Compare with previous version

unmarked as a Work In Progress

added 1 commit

• 48257d97 - (fix) Test regression from daily reward notification rewording - #1582

Compare with previous version

mentioned in merge request engine!293 (merged)

added 89 commits

• 48257d97...37ac7b64 - 87 commits from branch master
• ab2cd643 - Merge branch 'master' into feat/588-state-on-user
• c90ffa6f - (feat) Explanation of user states and multiplier values in wallet 101 - #1758

Compare with previous version

added 33 commits

• c90ffa6f...d69d2bd0 - 31 commits from branch master
• 3ae9aa12 - Merge branch 'master' into feat/588-state-on-user
• 8f28c461 - (chore) Linting recent changes

Compare with previous version

approved this merge request

Some feedback for you @gthouret

1. i would add the state they are currently in next to reward multiplier (contributions tab) with a tool tip explaining what the state means and maybe link to the explanation page on token 101

2. we may even want to display the user state on their channel publicly @markeharding @ottman

3. notifications is the main thing I would like to test somehow assuming the multipliers are working properly. ideally we can start to send notifications right BEFORE the user drops a user state, encouraging them to log in to avoid that happening. is there a way to read the notifications, or test this?

will keep thinking of other feedback.