Participants asked for the order history to have some sense of priority, because it's not immediately clear you start at the bottom or top and with a lot of messages its hard to spot the ones where the user successfully completed the checkout. I have started doing a design for this, but I would like to discuss the priorties.

We shouldn't be color coding each message, we should only color code important successes and important failures. Could anyone list all the messages that are possible? Besides successful payment, are there other successes?

CommentFileSizeAuthor
#2 order-complete.jpg139.21 KBBojhan

Comments

Bojhan’s picture

Assigned: Unassigned » guguss

Going to assign this for feedback

Bojhan’s picture

Assigned: guguss » Unassigned
StatusFileSize
new139.21 KB

I think, we should at the very least add "Complete" indicator.

order-complete.jpg

guguss’s picture

I think we should only 2 colors:

  • Green for order completed
  • Red for payment transaction failed
Bojhan’s picture

Yup, could we assign this to someone?

cookiz’s picture

Assigned: Unassigned » cookiz
cookiz’s picture

Assigned: Unassigned » Bojhan

Is it still relevant to have the background colors on the statuses ?

Bojhan’s picture

Assigned: cookiz » Unassigned

Yup, it will make just a bit more useable. Though I am afraid for it to work to status column should move to the left. I am not sure why it is on the right, it is identifiying information more important than ID etc.

theo_’s picture

Assigned: Bojhan » Unassigned

Bojhan : you are talking about the description column i guess, right ? If so, you are right, it's more relevant to have this column on the left.

We scratched our heads with Cookiz and what came out is : we need a view handler to handle this.
This commerce order view field handler should allow user to :
- Select through an options form what are the "good" statuses and what are the "wrong" statuses.
- Define the "good" and "wrong" status css class.

Then we can re-use the output of this handler to add a css class to the row, so we are able to theme it :)

mglaman’s picture

Category: Task » Feature request
Issue summary: View changes

Re-assigning to feature request, however wondering if this is a Commerce Backoffice issue.

andrew.mikhailov’s picture

Assigned: Unassigned » andrew.mikhailov
andrew.mikhailov’s picture

Assigned: andrew.mikhailov » Unassigned
mglaman’s picture

Project: Commerce Kickstart » Commerce Backoffice
Version: 7.x-2.x-dev » 7.x-1.x-dev

This belongs in the backoffice queue.