Closed Bug 897810 Opened 6 years ago Closed 6 years ago
Please add flag machine-state to the Release Engineering: Buildduty component
Release engineering needs to track the state of over 3500 machines. While all these machines may not be tracked directly in bugzilla at the outset, they end up in the Machine Management component when they need interaction. Since it could be releng, sheriffs, IT, or even developers (in the case of loan requests) filing or interacting with these bugs, releng would like a well-defined flag for machine-state that avoids the current hodge-podge of almost-correct (or non-existent) whiteboard entries. Flag name: machine-state Product: mozilla.org Component: Release Engineering: Machine Management Values: ---, on-loan, needs-reboot, needs-diagnostics, needs-reimage, needs-postimage, decommissioned No restrictions on setting the flag. '---' should be the default state.
We can get to this once we do the tracking flag migration away from custom fields in the backend (bug 880829). Right now we are hesitant to add any additional single-select fields because of the tracking flags. Thanks dkl
Depends on: 880829
is this field still required? if so, please provide the new product/component, as the RelEng product didn't exist at the time this bug was filed.
Yes, we'd still like it, please. The new Product: Component is Release Engineering: Buildduty.
Summary: Please add flag machine-state to the Release Engineering: Machine Management component → Please add flag machine-state to the Release Engineering: Buildduty component
I have made the code change needed for this task and committed. When the change is live (maybe this week), then I can actually add the custom field using the Bugzilla UI. Setting myself to needinfo to remind me to do so. Committing to: bzr+ssh://email@example.com/bmo/4.2 modified extensions/BMO/lib/Data.pm Committed revision 9186. dkl
The new custom field 'cf_machine_state' has been successfully created.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.