-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stage main #901
Stage main #901
Conversation
…nto cp4r3z-617-e2e-edit-user
…nto cp4r3z-617-e2e-edit-user
…nto cp4r3z-617-e2e-edit-user
…robot/Spoke into bchrobot-backwards-role-compatibility
… into bchrobot-message-attribution
…nto cp4r3z-617-e2e-edit-user
@shakalee14 tl;dr:
I did QA following these instructions:
Only part 4 failed. I wasn't able to save a custom opt out message in the admin settings panel. |
Hey @azuzunaga For Part 4: It looks like it is working - for that organization, you are an ADMIN and you need to be an OWNER in order to change organizational settings. In the console you probably received a we also added a call to invalidate the org cache when the opt out message is updated. |
…mponentWillUpdate
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
Caching/Optimization Branches:
#889, #876, #850, #833
Caching/Feature Integrated Branches:
#900, #898, #891
New Features:
#882 & #911
Bug Fixes
#905, #868, #828, #817, #880
Testing:
#881
Migrations:
#900 adds a migration to the campaign table :