Page MenuHomePhabricator

"Assigned To" field seems too visible on task creation page
Closed, ResolvedPublic

Description

Phabricator doesn't seem to have a simple vs. advanced task submission view, perhaps because it has no advanced features, but http://fab.wmflabs.org/maniphest/task/create/ contains a couple field most reporters don't care about and will be confused by.
In particular "Assigned To" is nowhere as important as "Projects" and reporters will typically not know the product name, let alone devs. "Points" is also pointless for most cases, but at least (despite jargon) it clearly encourages to leave blank: "Agile estimation points. Leave the default value if you don't know what to set".

Details

Reference
fl415

Related Objects

Event Timeline

flimport raised the priority of this task from to Low.Sep 12 2014, 1:40 AM
flimport set Reference to fl415.

aklapper wrote on 2014-06-15 12:49:22 (UTC)

Phabricator doesn't seem to have a simple vs. advanced task submission view

It is meant to be "simple enough". :)

Still good and valid point that average users won't be interested in Points and Assigned To.

aklapper wrote on 2014-06-26 13:25:21 (UTC)

We're between the two poles simplistic vs semantic: "I want a simple form" (GitHub offers Title and Comment, plus Assignee and Milestone slightly more hidden in dropdowns) and "I want a field for everything" (see Bugzilla's UI mess). We need to define where we want to be and how much effort we want to put into getting there.

For an average user, the assignee and points fields are pretty irrelevant. I don't feel able yet to judge if these two fields are also rather irrelevant for other personas than an average user.
So it would be great to hide these two fields for average users who report tasks. That requires being able to differentiate users from other personas, and I don't think we can easily do that.

Personally I like the Phabricator task creation form because it already exposes way less fields (and complexity) than Bugzilla. Might not be perfect, but already way better.

My current proposal is to leave the current task creation form as is for day 1, and to re-evaluate after a while if things work sufficiently, or if people get confused by those two fields, and what kind of people (personas) these are.
Or in short: Not blocking Day 1, but take a look again here after launching Phabricator.

Nemo_bis wrote on 2014-07-02 20:15:06 (UTC)

In MediaZilla, we used not to be able to create a bug in ASSIGNED status since short ago: I don't see how it can suddenly be crucial. Of course it should be available on editing (and editing is not that easy in Phabricator as it is in Bugzilla, but that's already reported separately).

aklapper wrote on 2014-07-03 20:49:44 (UTC)

I miss where somebody stated that it's crucial.

Nemo_bis wrote on 2014-07-17 19:29:26 (UTC)

I miss where somebody stated that it's crucial.

Someone seemed to imply that the loss of that "feature" would be an obstacle to fixing this bug.

qgil wrote on 2014-08-27 14:41:24 (UTC)

Now AllUsers don't get this field when creating a task, only those joining Triagers -- see T64#35

We are trying out this policy. If it stays, then this task would be solved.

greg wrote on 2014-09-07 05:44:01 (UTC)

Will the "Points" field be provided on at least the edit view of a task? I can't seem to find the points field in any task I created in the #Release_Engineering project.

qgil wrote on 2014-09-07 08:26:12 (UTC)

New/casual will not see any "Assigned To" field when creating tasks; only members of the Triagers team will (and anybody can join that team). Problem solved.

About the agile points field, I just created T646: Set up project filters.