| • flimport | |
| Jun 12 2014, 6:43 AM |
| F4028747: phabricator-take-action.png | |
| May 18 2016, 9:11 PM |
Task actions are, confusingly enough, under a "Add comment" header (this is covered by some previous report). Adding to confusion, the dropdown initial selection is "comment", which suggests the other selections exclude commenting (dropdowns list mutually exclusive options), while they don't. The initial selection should be "None" or something like that.
Found while cluelessly trying to figure out how to add CCs to http://fab.wmflabs.org/T167#28 .
Cf. T78830
I think at this point we have enough proof that, even if the behavior is not obvious, users have no problem discovering and handling the action after the very initial phase of Phabricator use.
For what is worth, we have a screencast in Phabricator/Help showing the different options: https://commons.wikimedia.org/wiki/File:Gciwikimedia4.webm
There is no clear indication of what should be fixed in Phabricator. When it comes to proposals to be upstreamed, they are more effective when they are precise.
Proposing to decline this task since we are not going to put own resources in improving this area. Specific requests to be upstreamed could be created as new tasks, or they could be directly reported upstream.
I think at this point we have enough proof that, even if the behavior is not obvious, users have no problem discovering and handling the action after the very initial phase of Phabricator use.
I see no evidence of this.
The initial selection should be "None"
So is the whole point of this task to change "Comment" in the default dropdown option by "None"? I disagree. Commenting is an action. None sounds like no action at all.
Anyway, I see no evidence about new task comment dropdown being confusing for regular Phabricator users, which are the ones that most likely will need to do anything other than simply commenting.
