Skip to content
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

Research spike: define safe mode and alert fixes needed #3856

Open
mms710 opened this issue Feb 21, 2019 · 2 comments
Open

Research spike: define safe mode and alert fixes needed #3856

mms710 opened this issue Feb 21, 2019 · 2 comments

Comments

@mms710
Copy link

mms710 commented Feb 21, 2019

As part of the rollback protection and response work, we need to do some fixes for alert mode. This ticket is to define the alert mode fixes needed so we can create other tickets to fix those issues

@mms710 mms710 added this to Needs Prioritization in Arborist Team via automation Feb 21, 2019
@mms710 mms710 moved this from Needs Prioritization to Sprint Backlog in Arborist Team Feb 21, 2019
@tromer
Copy link
Contributor

tromer commented Feb 26, 2019

Related to #3325 ("New network alert modes").

@zebambam
Copy link

zebambam commented Mar 4, 2019

Title of the ticket should be "Define safe mode fixes needed". Specifically, we need to list out all the bugs in the alert system and safe mode (including adding calls under that umbrella that are not currently covered.

@mms710 mms710 changed the title Define alert mode fixes needed Define safe mode fixes needed Mar 4, 2019
@mms710 mms710 moved this from Bugs/Security Issues/TechDebt Backlog to Arborist Product Priorities in Arborist Team Apr 4, 2019
@mms710 mms710 changed the title Define safe mode fixes needed Define safe mode and alert fixes needed May 14, 2019
@mms710 mms710 changed the title Define safe mode and alert fixes needed Research spike: define safe mode and alert fixes needed May 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Arborist Team
  
Arborist Product Priorities
Development

No branches or pull requests

3 participants