What a task "is" 
Thus,

Best-guess order of magnitude. 1 minute. 1 hour. 1 day. 1 week. 1 month. (Anything longer than
a month, and the task hasn't been sufficiently broken down into smaller
pieces.)



> More often than not, the goal of classifying things along those lines isn't
> about *what* the individual issue is, but whether it's in or out of
> scope. Whether something is in out of scope is a worthwhile facet for
> classification, but using bug vs. feature as a proxy for that confuses the
> issue. More often than not, in or out of scope is best handled through
> discussion, not simply reclassifying the issue. When that happens, 

 Think "separate but equal". 
>