-
-
Notifications
You must be signed in to change notification settings - Fork 473
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
Add a flag that is the type of request. #4175
Comments
@cielf I can take this ticket. |
Go for it! |
Would it be beneficial for there to be a default request type? If so which one?
EDIT |
That's right -- the type will be known before the request is created. |
@cielf are there any specific colors you would like each flag to be? I have included some screenshots of the request index and show pages as well as the export. |
Lets just have them all be normal text. They are just informational, and otherwise the users might think they are buttons. I would actually just call them quantity, individual and child as well (should have noticed that earlier). |
This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned. |
Automatically unassigned after 7 days of inactivity. |
Automatically unassigned after 7 days of inactivity. |
This is in the final throes of review. |
Automatically unassigned after 7 days of inactivity. |
Summary
Add a request type flag that will be visible to the banks
Why
The banks don't know which request types their partners are using. Knowing will help them supporting their partners
Details
Add a flag to request that will be set according to whether the request is a quantity request, a by-individuals request or a child-based request. Show this to the bank on their request view, and in the request export.
This would enable the banks to see, after a couple of cycles, whether any of their partners are using each request type, and be able to simplify the options available to their partners based on that information.
Criteria for completion
The text was updated successfully, but these errors were encountered: