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

Payment Timeline phase 2: capture the refund reason #753

Open
marcinbot opened this issue Jun 23, 2020 · 0 comments
Open

Payment Timeline phase 2: capture the refund reason #753

marcinbot opened this issue Jun 23, 2020 · 0 comments
Labels
category: projects For any issues which are part of any project, including bugs, enhancements, etc. component: timeline and events Issues related to Timeline and Events focus: payments acceptance & processing needs design The issue requires design input/work from a designer.

Comments

@marcinbot
Copy link
Contributor

marcinbot commented Jun 23, 2020

We'd like to show the refund reason in the payment timeline. Right now the reason entered when issuing a refund will only be converted to a Woo core order note. Is it possible to intercept that reason and add it to the refund's metadata when issuing it?

Also includes the server work and timeline rendering of the refund reason. Feel free to split into a separate issue if needed.

@marcinbot marcinbot added the component: timeline and events Issues related to Timeline and Events label Jun 23, 2020
@LevinMedia LevinMedia added the needs design The issue requires design input/work from a designer. label Jan 28, 2022
@jessy-p jessy-p added the category: projects For any issues which are part of any project, including bugs, enhancements, etc. label Feb 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: projects For any issues which are part of any project, including bugs, enhancements, etc. component: timeline and events Issues related to Timeline and Events focus: payments acceptance & processing needs design The issue requires design input/work from a designer.
Projects
None yet
Development

No branches or pull requests

4 participants