Page MenuHomePhorge

too many solutions for the task "archive"; lacking consistency
Closed, InvalidPublic

Description

How to reproduce:
go to Inbox. Select one mail.

Problem:
moving the mail to "archive" possible via:

  1. right klick -> archive
  2. top row on the right (next to "delete")
  3. drag and drop to folder "archive" on the left

General problem: if user uses first option here, they tend to use the same option for every other action/function, but sometimes this option is not available (-> consistency).

Solution:
Concentrate on one or two possible solutions which are available for every action similar to this one.

Hier evt. noch Beispiele aus eurem Protokoll einfügen, wann VP Rechtsklick verwendet hat und die gesuchte Funktion dort nicht gefunden hat.

Gerne anders formulieren. Will nur deutlich machen, dass man konsistent bleiben muss was Funktionen und Lösungswege an geht.

Details

Ticket Type
Task

Event Timeline

auch diese Variante von Archivieren ist möglich:

Bildschirmfoto 2018-01-26 um 15.39.30.png (364×770 px, 144 KB)

Ja da waren noch mehr aber die waren ja für bevor man eine Mail abschickt und das war eine andere Form von Archivieren laut @bohlender

ja, ich weiß. trotzdem ist es für den Nutzer nicht klar, wann was archiviert wird.

General problem: if user uses first option here, they tend to use the same option for every other action/function, but sometimes this option is not available (-> consistency).

In this case, the issue is not that we offer 3 options for archive, but that we don't consistently offer other functions this way.

What other functions are not consistent with this?

ja, ich weiß. trotzdem ist es für den Nutzer nicht klar, wann was archiviert wird.

bitte ein seperates ticket dafür

@NG I also think that the problem is the missing consistency in the rest of the program, not that several options are offered for one certain action (I do actually think that it is very good to have several options!)

We already have a ticket for: "consistently enable right-click" (T3514), so maybe we should/could only open up another ticket for (respectively change this one to): "consistently enable drag&drop"?

feel free to close this , once the other thing is in a new ticket

@NG
I am not sure whether drag&drop does actually not work for other parts of the program, so if you have more information about this, maybe you could make a corresponding ticket so that we can close this one?

bohlender moved this task from Backlog to Done on the UX Seminar WS17 board.