Bug management/Bug report life cycle/nan

This page describes the life of a task (bug report, feature requests, etc.) in.


 * When a task is first created, it is given the Open status.
 * When a task is actively being worked on, it can be given the In Progress status.
 * When a specific developer plans to work or works on a task, ideally the specific developer is set as assignee on the task.
 * If an initial patch for a task has been put into the Gerrit code review tool, the project Patch-For-Review is automatically added to the task. (See .)
 * Kiat-sok tsi̍t-ê jīm-bū:
 * A task is given the Resolved status when a code change that fixes the task has been merged in Gerrit. This does not mean that the fix is immediately available on a Wikimedia website as it can take up to two weeks.
 * A task is given the Declined status when the problem can not be reproduced, when missing information has not been provided, or when an acceptable workaround exists to achieve a similar outcome as requested. This status is also set when there's a consensus that implementing a particular task would be a bad idea. 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.



Uân-sîng jīm-bū
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.



Siánn-mih sî-tsūn guá ē-tàng sú-iōng siu-ho̍k tîng-sū (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.