BNGP-3724: Logic to check user status and paragraph suppression #637
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
https://eaflood.atlassian.net/browse/BNGP-3724 For the allocations journey, the view for checking a users Defra account displays two paragraphs of text currently regardless of how questions are answered. This change enhances allocation journey logic to take account of whether the user is not acting on behalf of a client and is not the landowner/leaseholder (non-relevant person) and suppresses the second paragraph if so.
thousand-leaves
changed the title
…on-relevant-person-check Updating branch from master
|
KiranVarma02
approved these changes
Feb 22, 2024
|
tested by Tajinder |
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.
https://eaflood.atlassian.net/browse/BNGP-3724
For the allocations journey, the view for checking a users Defra account displays two paragraphs of text currently regardless of how questions are answered. This change enhances allocation journey logic to take account of whether the user is not acting on behalf of a client and is not the landowner/leaseholder (non-relevant person) and suppresses the second paragraph if so.