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

Important UX/UI changes when users make Refunds. #2420

Open
4 tasks
Tracked by #32
agichim opened this issue May 17, 2021 · 1 comment
Open
4 tasks
Tracked by #32

Important UX/UI changes when users make Refunds. #2420

agichim opened this issue May 17, 2021 · 1 comment

Comments

@agichim
Copy link
Member

agichim commented May 17, 2021

After a refund has been made, the Refund button doesn't display anything too visible to the user that a refund has already been made.

I know the order states Cancelled on top on the left.
I know there is a Refund amount on the same line where the Refund button is.
I know that when you click Refund for a second time, the price field states the remaining balance that was not refunded instead of the total Order amount.

When you try to refund an amount which is higher than the total Order (refund going negative) the platform gives a 500 error.

Proposals to implement:

  • if a partial refund has been made, show next to the word Refund a number indicating how many times a Refund has been made. 1 Refund → image
  • if a total refund has been made, the button should be greyed out and not-clickable, keeping the number in parenthesis OR remove the number and change the wording from Refund to Refundedimage
  • the Cancelled tag on the top-left, should also change to Refund after a refund has been made. Of course, it should change across the platform, globally.
    image
  • the word completed should be green.
    image

Although a larger refund than the available amount cannot be made, I believe there should be some specificity like the one I mention above.

@Paul-Eraman-CoopCycle
Copy link
Contributor

@lucasferraro How difficult might this be?

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

No branches or pull requests

2 participants