#Bugzilla bug status workflow code#
* editproduct.cgi: There is code that looks at UNCONFIRMED bugs, with regards to voting. * ::Bug: CheckIfVotedConfirmed will be handled in Stage 3 There are also certain files that may be involved in workflows, but aren't involved in Stage 1. There are certain files that do references status, but which I am not going to touch. * list/ (which transitions are available to all bugs)Įach of the files listed above will have its code moved as part of a bug that is marked as blocking this bug. * bug/ (which transitions are available to this bug) * reports.cgi (change/remove the default-selected statuses) * (is the incoming bug's status valid for the product's workflow?) * (pull the list of statuses from the DB) * ::Bug (is_open_state, check_can_change_field) Note: multiple conditions in the action stanza are optional but at least one must be present.The following PLs/CGIs/PMs reference bug statuses in some way that is workflow-related: :Ĝode-Review flag added on Gerrit with values from -2 to +2 For positive values, you must not omit a leading +. : Verified flag added on Gerrit with values from -1 to +1 For positive values, you must not omit a leading +. :Ěction performed on Gerrit change-id, possible values are: created, commented, merged, abandoned, restored status/resolution STATUS/RESOLUTION change the associated bug's status to STATUS and resolution to RESOLUTION, where STATUS can be any of the values your bugzilla configuration allows to close bugs, and RESOLUTION can be any of the values your bugzilla configuration allows as resolution. Setting the resolution has only an effect if the associated bug is in a closed state. resolution RESOLUTION change the associated bug’s resolution to RESOLUTION, where RESOLUTION can be any of the values your bugzilla configuration allows as resolution. Be aware, that changing a bug from any status for open bugs to a status for closed bugs will not work, as the resolution would be missing. can be any of: status STATUS change the associated bug‘s status to STATUS, where STATUS can be any of the values your bugzilla configuration allows as status. :Ěction to perform on Bugzila issue when all the conditions in the stanza are met.
Syntax of the status transition configuration file is the following: Transition automation is driven by $GERRIT_SITE/nfig file. If it is not, the plugin will throw exceptions. When using this possibility, the plugin assumes that gerrit.canonicalWebUrl is set. Issues workflow automationīugzilla plugin is able to automate status transition on the issues based on code-review actions performed on Gerrit actions are performed on Bugzilla using the username/password provided during Gerrit init.
When Gerrit gitweb is configured, an additional direct link from Bugzilla to GitWeb will be created, pointing exactly to the Git commit ID containing the Bugzilla bug ID. Issue-id enforced in commit message : suggested Gerrit init example: *** Bugzilla connectivityīugzilla bug number regex +-+)]: Gerrit init integrationīugzilla plugin is integrated as a Gerrit init step in order to simplify and guide through the configuration of Bugzilla integration and connectivity check, avoiding bogus settings to prevent Gerrit plugin to start correctly. In order for Gerrit to connect to Bugzilla/XML-RPC url and credentials are required in your nfig / nfig under the section.īugzilla credentials and connectivity details are asked and verified during the Gerrit init. Note that the plugin relies on $1 holding the numeric id, so we cannot have match group 1 spanning over the whole “(Bug 4711)”.īe sure to label the commentLink “bugzilla” with lowercase “b” to match the config section's name below. Once a Git commit with a comment link is detected, the Bugzilla bug ID is extracted and a new comment added to the issue, pointing back to the original Git commit. OPTIONAL : Bug-ids are liked when found on git commit message, no warning are displayed otherwise. SUGGESTED : Whenever git commit message does not contain one or more issue-ids, a warning message is displayed as a suggestion on the client. MANDATORY : One or more issue-ids are required in the git commit message, otherwise the git push will be rejected. Git commits are associated to Bugzilla bugs reusing the existing Gerrit i 1 to extract the issue ID from commit comments.Īdditionally you need to specify the enforcement policy for git commits with regards to issue-tracker associations the following values are supported: Plugin plugin allows to associate Bugzilla bugs to Git commits thanks to the Gerrit listener interface.
0 kommentar(er)
