Is your feature request related to a problem? Please describe.
There is a problem with the current warning message when an admin clicks on REJECT for an account request. The language says: "Are you sure you want to deny this account request? User will not be allowed to request again." But that is not accurate because currently, a user can simply re-request an account using all the same information and the request will again appear in the queue on the Account Requests page.
Describe the solution you'd like
We need to update the language either to something like: "Are you sure you want to deny this account request? The user will have to resubmit their request if it is valid." or just remove the second sentence and leave the message as: "Are you sure you want to deny this account request?" This way, as an admin user, I can be better informed and more certain of what happens when I reject a request.
Describe alternatives you've considered
See above.
Additional context
Sarah said: "I am pretty sure that this used to be true [what the error message says now]. However, we were getting into a situation where so many people were blocked from rere requesting an account when they had been mistakenly rejected, that we made a change to sprout about a year and a half ago so that you are now able to make a request after being rejected. So given that probably the best approach to this issue is to change the error message if possible."
Prioritization Process
[x] Confirm the issue is a feature to which we want to devote resources.
[X] Write user story in as a (role) I want (something) so that (benefit) format.
[X] Label story Large, Uncertain, Small. If the story is too large, convert the story to a milestone/epic. SMALL story.
[ ] Label story as an active backlog issue (i.e. an issue on which we will be actively working).
[ ] Prioritize the story relative to other items in the active backlog.
[ ] Review progress/priorities in weekly collaboration meeting.
Is your feature request related to a problem? Please describe. There is a problem with the current warning message when an admin clicks on REJECT for an account request. The language says: "Are you sure you want to deny this account request? User will not be allowed to request again." But that is not accurate because currently, a user can simply re-request an account using all the same information and the request will again appear in the queue on the Account Requests page.
Describe the solution you'd like We need to update the language either to something like: "Are you sure you want to deny this account request? The user will have to resubmit their request if it is valid." or just remove the second sentence and leave the message as: "Are you sure you want to deny this account request?" This way, as an admin user, I can be better informed and more certain of what happens when I reject a request.
Describe alternatives you've considered See above.
Additional context Sarah said: "I am pretty sure that this used to be true [what the error message says now]. However, we were getting into a situation where so many people were blocked from rere requesting an account when they had been mistakenly rejected, that we made a change to sprout about a year and a half ago so that you are now able to make a request after being rejected. So given that probably the best approach to this issue is to change the error message if possible."
Prioritization Process
[x] Confirm the issue is a feature to which we want to devote resources.
[X] Write user story in
as a (role) I want (something) so that (benefit)format.[X] Label story Large, Uncertain, Small. If the story is too large, convert the story to a milestone/epic. SMALL story.
[ ] Label story as an active backlog issue (i.e. an issue on which we will be actively working).
[ ] Prioritize the story relative to other items in the active backlog.
[ ] Review progress/priorities in weekly collaboration meeting.