Following wishlist conversation that started here Enable quick capture of payments for a batch of orders but isolating that need so that we can move it forward.
Users are not able to identify easily who the orders belong to, which customer did order, as only the email info appears on the order line. Sometimes that email is pretty generic like “awesomepeople[a]something[dot]com”. So when they need to capture payments for multiple customers at once, it’s hard to do it, they have to search customer one by one, they can’t see at a glance and just capture action.
1- @Rachel suggested to try to remove a column and replace it by the first + family name column.
2- @sstead suggested to do like for products and order cycle, add a “columns” button to give the possibility to show or hide some columns.
After looking again at the table, I don’t see any info that could be removed from the table, they all seems pretty essential as “quick view” to understant at first sight the status and search for orders. Only the first and second name are missing, so I would be in favor of option 2.
Side comment on process:
It’s a pretty “quick win” so it would be great in our attempt to work together on priorizing things to test our new process candidate on it : 1- We had a wishlist (previous post) we see something more concrete with options and inception starting so that moves to icebox draft while inception are going on, when inception is finished and we have a clear feature candidate identify, we put it in the feature backlog as ready to prioritize and when prioritize enter the dev pipeline so moves to github.
Ping @danielle @Kirsten