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

TODO Implement notification for Oath Keeper #199

Open
tyagishuchi1 opened this issue Jun 18, 2020 · 4 comments
Open

TODO Implement notification for Oath Keeper #199

tyagishuchi1 opened this issue Jun 18, 2020 · 4 comments
Assignees
Labels
status:QA Dev work is completed and issue is up for QA testing
Milestone

Comments

@tyagishuchi1
Copy link

An oath keeper should be notified when the lock-in period is over and it is time to withdraw the oath.

Expected Behavior

The notification should appear in the Notifications page.

@ashishjur
Copy link

@mtmsuhail any idea on this one?

@ashishjur
Copy link

I'm removing myself from this as there is nothing (unknown) for me to work on this one. If needed please assign me to this issue.

@ashishjur ashishjur added this to the Oath Keeper milestone Jul 14, 2020
@ashishjur ashishjur assigned MirelXhafa and unassigned ashishjur Jul 14, 2020
mtmsuhail added a commit that referenced this issue Jul 22, 2020
@mtmsuhail mtmsuhail added the status:QA Dev work is completed and issue is up for QA testing label Jul 22, 2020
@tyagishuchi1 tyagishuchi1 removed the status:QA Dev work is completed and issue is up for QA testing label Jul 23, 2020
@tyagishuchi1
Copy link
Author

tyagishuchi1 commented Jul 23, 2020

Currently does not work on temp. Configure the server for it

@mtmsuhail
Copy link

@tyagishuchi1 that is a separate issue

@mtmsuhail mtmsuhail added the status:QA Dev work is completed and issue is up for QA testing label Aug 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:QA Dev work is completed and issue is up for QA testing
Projects
None yet
Development

No branches or pull requests

4 participants