**Rush** wrote on `2014-07-14 16:00:34 (UTC)`

> 
> Bugzilla-Phabricator mapping:
> 
> | Bugzilla | Phabricator |
> | ----- | ----- |
> | UNCONFIRMED (default) | Open + Needs Triage (default) |
> | NEW | Open |
> | ASSIGNED | Open + Assigned To |
> | PATCH_TO_REVIEW | Open + Code Revisions |
> | NEED_INFO | Needs Info |
> | RESOLVED FIXED | Resolved |
> | RESOLVED INVALID | Declined |
> | RESOLVED WONTFIX | Declined + project "Out Of Scope" |
> | RESOLVED WORKSFORME | Declined + project "Non Reproducible" |
> | RESOLVED DUPLICATE | (merged) |

I think this is a stupid question on my part, but are you suggesting a literal "out of scope" project that tasks are added to for this? or that there is a ticket state for which the option would be "declined - out of project scope'.  The first I don't think will work across the gamut just because it's too big of a bucket to be meaningful across all the projects / teams / workflows, etc,.  The second seems like a very specific category of declined? 

Declined does seems more diplomatic than won't fix :)

Work-for-me is a terrible state for a ticket to be in as it doesn't mean anything.  It just means two people had different experiences.  It doesn't mean something needs more work, and it doesn't mean something _doesn't_ need more work.  It's not a task or issue state so much as it could be the genesis of an open/closed state, yet is neither.  It doesn't seem meaningful, and could literally be a less valuable version of NEEDS_INFO.

INVALID = this cannot be done.

And, dear god please forgive me for even bikeshedding to this degree, but resolved fixed is less good than resolved closed (phab default).  Closed is wide enough to include hey we talked about it and decided it's a no, but good question.  Fixed implies changes...maybe only to me...whereas an issue can definitely be moved out of an open state without anything being modified other than a requesters state of mind :)

I think in some cases for resolved subtypes we are trying to cram a lot of information into this basic ticket state that doesn't necessarily fit there.  We could conceivably make a separate ticket field to indicate the resolved reasoning as in.

Resolved....

RATIONALE...wonfix/invalid/fixed/foo/bar/whatever/

The only thing I feel is a strong point is that invalid is a distinct state for a ticket to be in outside of normal resolution, and it is important to distinguish between this isn't possible and we are not doing this