Change Details

**Proposed statuses:** | **Status name in Phab** | **Explanation** | **Resembling in Bugzilla** | | open | Default state | {UNCONFIRMED, NEW, ASSIGNED, REOPENED, PATCH_TO_REVIEW*} {} | | needs_info | Stalled | | | resolved | A change that fixes the task has been merged. | {RESOLVED, VERIFIED, CLOSED} FIXED | | invalid | This is not a task, or it is out of scope in Wikimedia Phabricator. | {RESOLVED, VERIFIED, CLOSED} INVALID | | declined | Bad idea, can not be reproduced, missing information has not been provided, or an acceptable alternative exists. | {RESOLVED, VERIFIED, CLOSED} {WONTFIX, LATER, WORKSFORME} | | //(marked as duplicate)// | | RESOLVED DUPLICATE | *For PATCH_TO_REVIEW, create a project and add it to Phab tasks. See T277. --- --- For historical reasons: Initial task description: By default, Phabricator offers OPEN, RESOLVED, WONTFIX, INVALID as statuses (and we can resolve tasks as duplicates). Custom statuses can be added via /config/edit/maniphest.statuses/ Subtasks I see here: * Bugzilla also offers WORKSFORME (CANNOT_REPRODUCE). DO we want this? * NEEDINFO/NEEDS_MORE_INFO: marking an item as not actionable is a recurring request for Bugzilla, see https://bugzilla.wikimedia.org/show_bug.cgi?id=36064 * INVALID sounds harsh so we might want to bikeshed on a better wording.

**Proposed statuses:** | **Status name in Phab** | **Explanation** | **Resembling in Bugzilla** | | open | Default state | {UNCONFIRMED, NEW, ASSIGNED, REOPENED, PATCH_TO_REVIEW*} {} | | stalled | Stalled | | | resolved | A change that fixes the task has been merged. | {RESOLVED, VERIFIED, CLOSED} FIXED | | invalid | This is not a task, or it is out of scope in Wikimedia Phabricator. | {RESOLVED, VERIFIED, CLOSED} INVALID | | declined | Bad idea, can not be reproduced, missing information has not been provided, or an acceptable alternative exists. | {RESOLVED, VERIFIED, CLOSED} {WONTFIX, LATER, WORKSFORME} | | //(marked as duplicate)// | | RESOLVED DUPLICATE | *For PATCH_TO_REVIEW, create a project and add it to Phab tasks. See T277. --- --- For historical reasons: Initial task description: By default, Phabricator offers OPEN, RESOLVED, WONTFIX, INVALID as statuses (and we can resolve tasks as duplicates). Custom statuses can be added via /config/edit/maniphest.statuses/ Subtasks I see here: * Bugzilla also offers WORKSFORME (CANNOT_REPRODUCE). DO we want this? * NEEDINFO/NEEDS_MORE_INFO: marking an item as not actionable is a recurring request for Bugzilla, see https://bugzilla.wikimedia.org/show_bug.cgi?id=36064 * INVALID sounds harsh so we might want to bikeshed on a better wording.

**Proposed statuses:** | **Status name in Phab** | **Explanation** | **Resembling in Bugzilla** | | open | Default state | {UNCONFIRMED, NEW, ASSIGNED, REOPENED, PATCH_TO_REVIEW*} {} | | needs_info| stalled | Stalled | | | resolved | A change that fixes the task has been merged. | {RESOLVED, VERIFIED, CLOSED} FIXED | | invalid | This is not a task, or it is out of scope in Wikimedia Phabricator. | {RESOLVED, VERIFIED, CLOSED} INVALID | | declined | Bad idea, can not be reproduced, missing information has not been provided, or an acceptable alternative exists. | {RESOLVED, VERIFIED, CLOSED} {WONTFIX, LATER, WORKSFORME} | | //(marked as duplicate)// | | RESOLVED DUPLICATE | *For PATCH_TO_REVIEW, create a project and add it to Phab tasks. See T277. --- --- For historical reasons: Initial task description: By default, Phabricator offers OPEN, RESOLVED, WONTFIX, INVALID as statuses (and we can resolve tasks as duplicates). Custom statuses can be added via /config/edit/maniphest.statuses/ Subtasks I see here: * Bugzilla also offers WORKSFORME (CANNOT_REPRODUCE). DO we want this? * NEEDINFO/NEEDS_MORE_INFO: marking an item as not actionable is a recurring request for Bugzilla, see https://bugzilla.wikimedia.org/show_bug.cgi?id=36064 * INVALID sounds harsh so we might want to bikeshed on a better wording.