3 ms·
With regards to the products ux, one thing that I don't understand from the video: why does a tag for a ticket need to be dragged on to a ticket, why not a simp
by citricsquid 15y ago
With regards to the products ux, one thing that I don't understand from the video: why does a tag for a ticket need to be dragged on to a ticket, why not a simple "click tag click ticket" system?
The only reason dragging should really exist is when there is the potential for the decision to change, where up until the point where the drop is executed the decision is undecided.
The best way to do it would be a simple system where the agent clicks on the tag then clicks on the ticket and that ticket now has that tag; if you have to drag and drop it requires precision and extra attention to be paid; it's much easier to drop a tag in the wrong place than it is to click, because people have different expectations about which part needs to match. The only way to solve this would be to have the ticket that the drop is about to be executed on highlighted when the tag is over it, but even then that's more work than it is for click tag.
- prateekdayal 15y agoWow. Never thought about it that way. The decision to have it drag and drop comes from the fact that Gmail does it that way too and we wanted to stay as close to Gmail as possible to avoid any kind of learning curve. One thing that we are missing and will add is the row on which you are dropping getting highlighted when you move the label over it. Gmail does that.