#BUGZILLA BUG STATUS WORKFLOW PATCH#
#BUGZILLA BUG STATUS WORKFLOW LICENSE#

Conditionsīugs must meet specific conditions to be eligible for the action. However, workflow actions are useful to make.

#BUGZILLA BUG STATUS WORKFLOW PATCH#

The suggestion is to have fix released at patch being in code review and fix committed at merge. Some dev change the status to resolved fixed when the push the fix to gerrit for code review, some don't change it until a merge, and some forget at all. If not specified the action name is used to generate the identifier.īelow is the explanation of the action script syntax and tags. Even if you dont change workflow.xml, you still will be able to change status for a bug using Edit Bug dialog. Please add those statuses to bugzilla for easier track of real bug status. This identifier can be used to apply one window configuration for several actions. Optionally an action may contain the windowId child tag, which defines the window identifier used to refer to the visual properties of the action window (for example, size, position, etc). In my workflow, having a bug in the NEW state means that it's newly assigned to me (either b/c it's newly entered, or because it's been reassigned), and I still need to review it. These tables show the possible values of these fields and the valid transitions of the status field. In Bugzilla 3.2, reassigning a bug has no effect on the status. The script may contain both defined actions (for example, change the status value to Closed for the Close action) and actions, which require user input (for example, get the user comment when the bug status is changed). If a bug has a status which shows it has been resolved, it also has a resolution (otherwise the resolution field is empty). The set tag, which defines the action script which runs when the action is applied.Action applicability can be defined either by referring to the condition defined earlier or by specifying a filter statement using the filter tag and the same syntax as is used for the condition definition. I'm marking this as wontfix until somebody comes up with a doc patch. I don't think we want to change to the new status flow as it will lose some information for historical bugs, at least not unless all project agree to switch to the new flow. Action applicability condition, which defines which conditions a bug must meet to be eligible for the action. Yes, it comes from the bugzilla installation.The name tag, which defines the name of the action shown in the UI components (for example, Workflow combo box).If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.It consists of three mandatory sub-elements: Use thereof is explained in our trademark policy (see Project:Copyrights for details). Their respective logos and icons are also subject to international copyright laws. 'LibreOffice' and 'The Document Foundation' are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries.

#BUGZILLA BUG STATUS WORKFLOW LICENSE#

This does not include the source code of LibreOffice, which is licensed under the GNU Lesser General Public License ( LGPLv3). Only one bug status cannot be renamed nor deleted.

Please note that all contributions to The Document Foundation Wiki are considered to be released under the Creative Commons Attribution-ShareAlike 3.0 Unported License, unless otherwise specified. The bug status workflow is no longer hardcoded but can be freely customized from the web interface.

Based on work by Raal Raal and Dennis Roczek and others.

This page was last edited 19:10:35, by Ilmari Lauhakangas.

We dont have any equivalent to this status in bugzilla, creating this. If you see someone changing the status to ASSIGNED in an easy hack that is meant for multiple successive or parallel developers, change the status back to NEW and reset the Assignee. Pushing a commit with a proposed fix should change the bug status to fix released. However, this only makes sense for easy hacks that concern one single thing and not a repetitive task.

The first action performed by Bugzilla is assigning a unique numeric identifier. New developers solving easy hacks may also assign bugs to themselves. a new bug is discovered, its life be- gins in the UNCONFIRMED status. 'Please create a bug about XYZ and assign it to me' or 'Yeah, I'll take that bug please assign it to me.' In such cases, there won't need to be a two-step process: The developer has already agreed to accept the bug. In some cases someone will ask you to assign a bug directly to them - e.g. In our workflow, we usually just CC a developer and allow them to assign the bug to themselves if they'd like to tackle it. In some bug workflows, QA assigns NEW bugs to developers (by setting the Assigned To field), and then developers accept the assignment by changing the status field to ASSIGNED. This page is about the ASSIGNED state of the Status Field in Bugzilla.ĭevelopers use the ASSIGNED status to signal that they are working on a bug or enhancement request.

Bugzilla bug status workflow