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

Notification for changes to NetDebitCap or Position adjustments #517

Closed
15 of 16 tasks
elnyry-sam-k opened this issue Oct 18, 2018 · 2 comments
Closed
15 of 16 tasks
Assignees
Labels
Milestone

Comments

@elnyry-sam-k
Copy link
Member

elnyry-sam-k commented Oct 18, 2018

Goal:
As a Hub Operator
I would like to provide notifications for changes to NetDebitCap or Position adjustments
so that participating FSPs and the Hub Operator can be informed

Tasks:

Acceptance Criteria:

  • A notification (or notifications) is (/are) sent to an FSP when a change is made to the Net Debit Cap or Position adjustment is done
  • A notification (or notifications) is (/are) sent to an FSP when a Position adjustment is done
  • Both FSPs and the Hub Operator receive these alerts/notifications

PRs

  • [ ]

Dependencies:

Accountability:

@elnyry-sam-k elnyry-sam-k changed the title Notification for changes to NDC or Position Notification for changes to NetDebitCap or Position Oct 18, 2018
@elnyry-sam-k elnyry-sam-k changed the title Notification for changes to NetDebitCap or Position Notification for changes to NetDebitCap or Position adjustments Oct 19, 2018
@elnyry-sam-k elnyry-sam-k modified the milestones: Sprint 3.10, Sprint 4.1 Nov 20, 2018
@elnyry-sam-k
Copy link
Member Author

Moving to 4.1 to complete automated tests and deployment related tasks

@elnyry-sam-k
Copy link
Member Author

Increased estimate because of the tasks involving helm charts/helm, integration with email-notifier and other services. testing on the AWS deployment, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants