DEVOPS-43: Responder Portal Support Limits #2504
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket: https://emcr.atlassian.net/browse/DEVOPS-43
First pass on Support Limits functionality in responder portal.
When a task is queried from the backend, it now passes along information about the support limits for that task.
In the portal, a check is done when a support is being issued or extended which checks several conditions including whether support limits are defined, if extensions are available, and if the household member has already received this type of support in the defined period for the same file.
Future work will check across multiple tasks and files for duplicate supports once the fuzzy search work in DEVOPS-36 is complete.