Bug management/Bug report life cycle/zh

本页描述了中一项任务（包括而不限于错误报告、功能请求等）的生命周期.


 * 对于新建的任务，其的状态为Open（开放）.
 * 有人正在尝试完成一项任务时，其的状态可以修改为In Progress（进行中）.
 * 当特定的开发者计划完成或正在进行某一项任务时，请尽可能地将这名开发者设定为此任务的assignee.
 * 当某项任务有对应的-{zh-hans:补丁;zh-hant:修補程式}-上传至Gerrit代码审阅工具时，项目Patch-For-Review会自动添加至此任务. （参见）
 * 关闭一项任务：
 * 一项任务对应的代码修改已在Gerrit上合并时，任务会以Resolved（已解决）状态关闭. 这并不意味着修复将会立即在维基媒体下属网站上生效——您可能需要等待至多两周的时间.
 * 当任务中所指出的问题无法复现、未能提供缺失的信息，或是已经存在一个与请求的功能类似的解决方案时，任务会以Declined（拒绝）状态关闭. 当已达成共识，认为这一任务是一个坏主意时，任务也会以本状态关闭.  For example, when a task contradicts a particular project's scope or the principles of the project and fixing would be barred from approval by the project's maintainers (or product managers, if existing). Depending on the specifics, a user preference, a global configuration variable, a re-implementation, or forking the code can be alternatives to marking a task as declined.
 * A task is given the Invalid status when the task does not describe an actual wrong behavior, or when it is a change that is outside the power of the component's developers. For example, tasks proposing changes to third-party software or third-party website settings are INVALID, as well as requests contrary to legal or contractual obligations.
 * A task is given the Duplicate status when the task has been reported before and has been merged into another task, no matter if the other task has been already resolved or not.
 * Optionally the keyword Verified is set if a QA tester or the task author confirmed the merged fix in Gerrit after it had been deployed.
 * If a task was marked as Resolved and it turns out that this was incorrect, the task's status can be changed back to Open.
 * If a task is waiting for further input (e.g. from the task author or a third party like upstream) and can currently not be acted on, the Stalled status is temporarily given. The Stalled status can also be given when a task is waiting for its subtask(s) to be resolved first.

Completing tasks
Different teams complete the work on tasks differently, see. Some move it to a Done column on a project workboard after QA and product management have reviewed the change, and only change the task status to Resolved when they complete the current "sprint" or when the code is available in production. Others change the task status to Resolved the moment a code change that completes a task is merged, leaving its tags and workboard column unchanged.

When can I use the fix
The short answer for Wikimedia websites is: Somewhere between a week and three weeks after the task has been closed as Resolved. For details, see Deployments.