Page MenuHomePhabricator

Use more explicit language for unassigning tasks

Authored by epriestley on Mar 10 2016, 2:48 AM.
Referenced Files
Unknown Object (File)
Sun, Nov 27, 12:11 AM
Unknown Object (File)
Fri, Nov 11, 10:02 PM
Unknown Object (File)
Thu, Nov 10, 7:25 AM
Unknown Object (File)
Nov 4 2022, 6:55 PM
Unknown Object (File)
Oct 19 2022, 11:28 PM
Unknown Object (File)
Oct 10 2022, 8:47 AM
Unknown Object (File)
Oct 1 2022, 5:09 PM
Unknown Object (File)
Sep 26 2022, 12:42 AM



Ref T10493.

  • Call this action "Unassigned" instead of "Up For Grabs", since the latter implies that it's OK for anyone to grab it, which is a social/context thing that we probably shouldn't assume.
  • Show who a task was previously assigned to in the transaction.

The text is a little clunky, yell if you've got a better wording? Or maybe I'll come up with something.

Test Plan

Screen Shot 2016-03-09 at 6.46.37 PM.png (78×376 px, 14 KB)

Diff Detail

rP Phabricator
Lint Not Applicable
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Use more explicit language for unassigning tasks.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Mar 10 2016, 2:50 AM

Some alternate, equally clunky wordings:

cat unassigned dog from this task.
cat unassigned this task, evicting dog from the seat of power.
cat reassigned this task from dog to no one.
cat unassigned this task, which was previously assigned to dog.

I'm still thinking about it

this is pretty important

what if I get it wrong and everyone laughs at me?

cat unassigned this task, evicting dog from the seat of power.


This revision was automatically updated to reflect the committed changes.