+++ This bug was initially created as a clone of Bug #540931 +++ For tracking Thunderbird 3.1.next releases we'd like to have multi-state custom flags similar to the ones used for Firefox (e.g. status1.9.2 and blocking1.9.3). Please create blocking-thunderbird3.2 and status-thunderbird3.2 as detailed below. Products for flags to appear in: - Thunderbird - MailNews Core - Mozilla Messaging blocking-thunderbird3.2 initial values: - '?' - '-' - 'needed' - '.alpha1+' The '?' value should be restricted to the thunderbird-trusted-requesters group, as per bug 557751. Please restrict the other statuses to the thunderbird-drivers group only. status-thunderbird3.2 initial values: - '?' - 'unaffected' - 'wontfix' - 'wanted' - 'alpha1-fixed' Please restrict 'wanted' setting to the thunderbird-drivers group. The other flags should be restricted to people belonging to the 'canconfirm' group.
Getting these created within the next week or so would be very useful ;-) Thanks.
Added (blocking|status)-thunderbird3.2 to quicksearch. Committing to: bzr+ssh://bzr.mozilla.org/bmo/3.4/ modified Bugzilla/Search/Quicksearch.pm Committed revision 6795.
Status: NEW → ASSIGNED
Tried to create these fields twice and ran into issues. This is going to have to wait until justdave gets back from vacation next week so he can help me debug this.
Update: Please create flags as per comment 1. Additionally please create the following flag: blocking-thunderbird3.2.next with initial values: - '?' - '-' - 'needed' - '.alpha1+'
Summary: Create multi-state custom flags for Thunderbird 3.1.next development (blocking and status fields) → Create multi-state custom flags for next parts of Thunderbird development
Just tried to do this again. Got an ISE 500. Asked dave to check server error logs to help track this bug down.
The error in the log was a duplicate key error saying it already existed. And indeed it does, and all of the pieces look intact. Did you submit twice perhaps? As far as I can tell it looks done.
(In reply to comment #6) > The error in the log was a duplicate key error saying it already existed. And > indeed it does, and all of the pieces look intact. Did you submit twice > perhaps? As far as I can tell it looks done. No, I submitted only once. It may look correct, but it's not, as I can't add any field values to it. visibility_value_id is not a valid parameter for the Bugzilla::Field::Choice::cf_blocking_thunderbird32::create function.
Done for now with some help from manual SQL statements. Sorry about the ridiculous delay in getting to this.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.