Page MenuHomePhabricator

Use more explicit language for unassigning tasks
ClosedPublic

Authored by epriestley on Mar 10 2016, 2:48 AM.

Details

Summary

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

Diff Detail

Repository
rP Phabricator
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

epriestley updated this revision to Diff 37244.Mar 10 2016, 2:48 AM
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 accepted this revision.Mar 10 2016, 2:50 AM
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.

+1

This revision was automatically updated to reflect the committed changes.