BZ::Cl...agType(3pm)
๐ BZ::Client::FlagType(3pm) โ User Contributed Perl Documentation ๐
okay bestie, this is part 1 of the BZ::Client::FlagType manual, and it is literally giving โI know every flag in Bugzillaโ energy. no cap, every detail is staying right here. ๐ซถ
๐ธ NAME ๐ธ
BZ::Client::FlagType - The API for creating, changing, and getting info on Flags
๐ VERSION ๐
version 4.91
โจ SYNOPSIS โจ
This class provides methods for accessing and managing Flags in Bugzilla.
my $client = BZ::Client->new( url => $url,
user => $user,
password => $password );
my %results = BZ::Client::FlagType->get( $client, \%params );
my $id = BZ::Client::FlagType->create( $client, \%params );
my @updates = BZ::Client::FlagType->update( $client, \%params );
๐ CLASS METHODS ๐
This section lists the class methods, which are available in this module.
๐ get ๐
$id = BZ::Client::FlagType->get( $client, \%params );
Get information about valid flag types that can be set for bugs and attachments.
๐ History ๐
Added in Bugzilla 5.0.
๐ Parameters ๐
You must pass a product name and an optional component name.
productโ product (string) The name of a valid product.componentโ component (string) An optional valid component name associated with the product.
๐ฆ Returns ๐ฆ
A hash containing two keys, bug and attachment. Each key value is an array of hashes, containing the following keys:
idโ id (int) An integer ID uniquely identifying this flag type.nameโ name (string) The name for the flag type.typeโ type (string) The target of the flag type which is eitherbugorattachment.descriptionโ description (string) The description of the flag type.valuesโ values (array) An array of string values that the user can set on the flag type.is_requesteebleโ is_requesteeble (boolean) Users can ask specific other users to set flags of this type. (yes, it really saysis_requesteeblein the return list โ we do not correct the APIโs spelling, bestie ๐ )is_multiplicableโ is_multiplicable (boolean) Multiple flags of this type can be set for the same bug or attachment.
๐ Errors ๐
106- Product Access Denied โ Either the product does not exist or you donโt have access to it.51- Invalid Component โ The component provided does not exist in the product.
๐ create ๐
$id = BZ::Client::FlagType->create( $client, \%params );
This allows you to create a new Flag Type in Bugzilla.
โ ๏ธ Marked as unstable as of Bugzilla 5.0.
Added in Bugzilla 5.0.
๐ Parameters ๐
Some params must be set, or an error will be thrown. These params are noted as Required.
nameโ name (string) A short name identifying this type. Required.descriptionโ description (string) A comprehensive description of this type. Required.inclusionsโ inclusions (array) An array of strings or a hash containing product names, and optionally component names. If you provide a string, the flag type will be shown on all bugs in that product. If you provide a hash, the key represents the product name, and the value is the components of the product to be included.
For example:
[ 'FooProduct',
{
BarProduct => [ 'C1', 'C3' ],
BazProduct => [ 'C7' ]
}
]
This flag will be added to All components of FooProduct, components C1 and C3 of BarProduct, and C7 of BazProduct.
exclusionsโ exclusions (array) An array of strings or hashes containing product names. This uses the same format asinclusions. This will exclude the flag from all products and components specified.sortkeyโ sortkey (int) A number between1and32767by which this type will be sorted when displayed to users in a list; ignore if you donโt care what order the types appear in or if you want them to appear in alphabetical order.is_activeโ is_active (boolean) Flag of this type appear in the UI and can be set. Default istrue.is_requestableโ is_requestable (boolean) Users can ask for flags of this type to be set. Default istrue.cc_listโ cc_list (array) An array of strings. If the flag type is requestable, who should receive e-mail notification of requests. This is an array of e-mail addresses which do not need to be Bugzilla logins.is_specifically_requestableโ is_specifically_requestable (boolean) Users can ask specific other users to set flags of this type as opposed to just asking the wind. Default istrue.is_multiplicableโ is_multiplicable (boolean) Multiple flags of this type can be set on the same bug. Default istrue.grant_groupโ grant_group (string) The group allowed to grant/deny flags of this type (to allow all users to grant/deny these flags, select no group). Default is no group.request_groupโ request_group (string) If flags of this type are requestable, the group allowed to request them (to allow all users to request these flags, select no group). Note that the request group alone has no effect if the grant group is not defined! Default is no group.
๐ฆ Returns ๐ฆ
The ID of the newly-created group.
๐ Errors ๐
51- Group Does Not Exist โ The group name you entered does not exist, or you do not have access to it.105- Unknown component โ The component does not exist for this product.106- Product Access Denied โ Either the product does not exist or you donโt have editcomponents privileges to it.501- Illegal Email Address โ One of the e-mail address in the CC list is invalid. An e-mail in the CC list does NOT need to be a valid Bugzilla user.1101- Flag Type Name invalid โ You must specify a non-blank name for this flag type. It must no contain spaces or commas, and must be 50 characters or less.1102- Flag type must have description โ You must specify a description for this flag type.1103- Flag type CC list is invalid โ The CC list must be 200 characters or less.1104- Flag Type Sort Key Not Valid โ The sort key is not a valid number.1105- Flag Type Not Editable โ This flag type is not available for the products you can administer. Therefore you can not edit attributes of the flag type, other than the inclusion and exclusion list.
๐ฅ update ๐ฅ
@results = BZ::Client::FlagType->update( $client, \%params );
$results = BZ::Client::FlagType->update( $client, \%params );
This allows you to update a flag type in Bugzilla.
๐ History ๐
Added in Bugzilla 5.0.
๐ Parameters ๐
Note: The following parameters specify which products you are updating. You must set one or both of these parameters.
idsโ ids (array of ints) Numeric ids of the flag types that you wish to update.namesโ names (array of strings) Names of the flag types that you wish to update. If many flag types have the same name, this will change ALL of them.
Note: The following parameters specify the new values you want to set for the products you are updating.
nameโ name (string) A short name identifying this type.descriptionโ description (string) A comprehensive description of this type.inclusionsโ An array of strings or a hash containing product names, and optionally component names.
If you provide a string, the flag type will be shown on all bugs in that product.
If you provide a hash, the key represents the product name, and the value is the components of the product to be included.
For example:
[ 'FooProduct',
{
BarProduct => [ 'C1', 'C3' ],
BazProduct => [ 'C7' ]
}
]
This flag will be added to all components of FooProduct, components C1 and C3 of BarProduct, and C7 of BazProduct.
exclusionsโ An array of strings or hashes containing product names.
This uses the same fromat as inclusions.
This will exclude the flag from all products and components specified.
sortkeyโ sortkey (int) A number between1and32767by which this type will be sorted when displayed to users in a list; ignore if you donโt care what order the types appear in or if you want them to appear in alphabetical order.is_activeโ is_active (boolean) Flag of this type appear in the UI and can be set.is_requestableโ is_requestable (boolean) Users can ask for flags of this type to be set.cc_listโ cc_list (array) An array of strings. If the flag type is requestable, who should receive e-mail notification of requests. This is an array of e-mail addresses which do not need to be Bugzilla logins.is_specifically_requestableโ is_specifically_requestable (boolean) Users can ask specific other users to set flags of this type as opposed to just asking the wind.is_multiplicableโ is_multiplicable (boolean) Multiple flags of this type can be set on the same bug.grant_groupโ grant_group (string) The group allowed to grant/deny flags of this type (to allow all users to grant/deny these flags, select no group).request_groupโ request_group (string) If flags of this type are requestable, the group allowed to request them (to allow all users to request these flags, select no group).
Note that the request group alone has no effect if the grant group is not defined!
๐ฆ Returns ๐ฆ
An array of hashes with the following fields:
idโ id (int) The ID of the product that was updated.nameโ name (string) The name of the product that was updated.changesโ changes (hash) The changes that were actually done on this product.
The keys are the names of the fields that were changed, and the values are a hash with two keys:
addedโ added (string) The value that this field was changed to.removedโ removed (string) The value that was previously set in this field.
Note that booleans will be represented with the strings 1 and 0.
Hereโs an example of what a return value might look like:
[
{
id => 123,
changes => {
name => {
removed => 'FooFlagType',
added => 'BarFlagType'
},
is_requestable => {
removed => '1',
added => '0',
}
}
}
]
๐ Errors ๐
51- Group Does Not Exist โ The group name you entered does not exist, or you do not have access to it.105- Unknown component โ The component does not exist for this product.106โ Product Access Denied ๐ซ So either that product straight up doesn't exist, or you don't haveeditcomponentsprivileges on it. Like, no keys to that door, bestie.501โ Illegal Email Address ๐ง One of the e-mail addresses chilling in the CC list is invalid. And here's the tea: an e-mail in the CC list does NOT need to be a valid Bugzilla user. Wild but true.1101โ Flag Type Name invalid ๐ท๏ธ You gotta give this flag type a non-blank name. It must not contain spaces or commas, and it has to be 50 characters or less. Three strikes and it's out.1102โ Flag type must have description ๐ Yeah, you actually have to write a description for this flag type. Non-negotiable.1103โ Flag type CC list is invalid ๐ฎ The CC list has a hard cap: 200 characters or less. Keep it cute and concise.1104โ Flag Type Sort Key Not Valid ๐ข The sort key isn't a valid number. It's giving "I typed vibes where digits should be."1105โ Flag Type Not Editable ๐ This flag type isn't available for the products you can administer. So you literally can't edit its attributes โ the only things you're allowed to touch are the inclusion and exclusion list. That's the whole menu, sorry babe.
๐ฆ INSTANCE METHODS
FIXME Not yet implemented ๐ซ
Like, not a single one yet. It's coming, bestie, it's just not here yet. Manifesting.
๐ EXCEPTION HANDLING
See BZ::Client::Exception. That's where all the catching-your-errors lore lives. Go read it, iykyk ๐
๐ SEE ALSO
BZ::ClientBZ::Client::API- Bugzilla API <https://www.bugzilla.org/docs/tip/en/html/api/Bugzilla/WebService/FlagType.html>
Pls go click around, there's so much more where this came from โจ
๐ AUTHORS
- Dean Hamstead <dean@bytefoundry.com.au>
- Jochen Wiedmann <jochen.wiedmann@gmail.com>
Legends, honestly. We stan ๐ซถ
๐ COPYRIGHT AND LICENSE
This software is copyright (c) 2026 by Dean Hamstad.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. Free free free, periodt ๐
And that's a wrap, bestie! ๐ฆ This little gem is BZ::Cl...agType(3pm), freshly minted with perl v5.40.2 and dated 2026-07-16 โ bookmark it, screenshot it, send it to the group chat ๐๐ธ
๐ฆ where this page comes from
- epel 10: perl-BZ-Client 4.9100-2.el10_3 ยท GPL-1.0-or-later OR Artistic-1.0-Perl
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms