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

Ability to see what users are making changes to the order #5

Open
4 tasks
Flyingmana opened this issue Aug 15, 2021 · 2 comments
Open
4 tasks

Ability to see what users are making changes to the order #5

Flyingmana opened this issue Aug 15, 2021 · 2 comments
Labels
Sponsored Issues which in one way or another are sponsored (details should be inside the Issue)

Comments

@Flyingmana
Copy link
Contributor

Ability to see which users are making changes to the order (Show in the order log area of Comments History)

normally the order comments do not log the author on admin side (see DB.sales_flat_order_status_history). Therefore we need to add this information.
As this is not (yet) a core module, this will happen in a separate table, linked to the sales_flat_order_status_history Table.
For Design it should be considered the comments can be created from different contexts (Admin, Frontend, Cron, ...), but relevant is only admin for now.

  • create new Table extending sales_flat_order_status_history with metadata about the author, no foreign keys
  • actions from the admin area should log the current admin userId, and a context
  • the Admin OrderView should show the Admin Name on the comment entry
  • this needs to be in the base module of this extension (the other features of this Extension could be in separate modules, see more in main ticket)
@Flyingmana Flyingmana added the Sponsored Issues which in one way or another are sponsored (details should be inside the Issue) label Aug 15, 2021
@elidrissidev
Copy link
Member

create new Table extending sales_flat_order_status_history with metadata about the author, no foreign keys

@Flyingmana May I ask what you mean by no foreign keys? on the user id column only or on the whole table?

@Flyingmana
Copy link
Contributor Author

on the whole table.
Reason is to not have it coupled to close with the core and avoid anything which could make upgrading harder in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Sponsored Issues which in one way or another are sponsored (details should be inside the Issue)
Projects
None yet
Development

No branches or pull requests

2 participants