maintainer
maxattachmentsize
maxlocalattachment
- musthavemilestoneonaccept
noresolveonopenblockers
password_complexity
rememberlogin
C<maintainer>,
C<maxattachmentsize>,
C<maxlocalattachment>,
- C<musthavemilestoneonaccept>,
C<noresolveonopenblockers>,
C<password_complexity>,
C<rememberlogin>,
{ old => $old_status ? $old_status->name : undef,
new => $new_status->name, field => 'bug_status' });
}
-
- if (ref $invocant
- && ($new_status->name eq 'IN_PROGRESS'
- # Backwards-compat for the old default workflow.
- or $new_status->name eq 'ASSIGNED')
- && Bugzilla->params->{"usetargetmilestone"}
- && Bugzilla->params->{"musthavemilestoneonaccept"}
- # musthavemilestoneonaccept applies only if at least two
- # target milestones are defined for the product.
- && scalar(@{ $product->milestones }) > 1
- && $invocant->target_milestone eq $product->default_milestone)
- {
- ThrowUserError("milestone_required", { bug => $invocant });
- }
if (!blessed $invocant) {
$params->{everconfirmed} = $new_status->name eq 'UNCONFIRMED' ? 0 : 1;
default => 1
},
- {
- name => 'musthavemilestoneonaccept',
- type => 'b',
- default => 0
- },
-
{
name => 'commentonchange_resolution',
type => 'b',
maintainer
maxattachmentsize
maxlocalattachment
- musthavemilestoneonaccept
password_complexity
rememberlogin
requirelogin
C<maintainer>,
C<maxattachmentsize>,
C<maxlocalattachment>,
- C<musthavemilestoneonaccept>,
C<password_complexity>,
C<rememberlogin>,
C<requirelogin>,
letsubmitterchoosemilestone
If this is on, then people submitting bugs can choose the Target Milestone for that bug. If off, then all bugs initially have the default milestone for the product being filed in.
-musthavemilestoneonaccept
- If you are using Target Milestone, do you want to require that the milestone be set in order for a user to set a bug's status to IN_PROGRESS?
-
commenton*
All these fields allow you to dictate what changes can pass
without comment and which must have a comment from the
"maintainer" : "admin@example.com",
"maxattachmentsize" : "1000",
"maxlocalattachment" : "0",
- "musthavemilestoneonaccept" : "0",
"password_complexity" : "no_constraints",
"rememberlogin" : "on",
"requirelogin" : "0",
* maintainer
* maxattachmentsize
* maxlocalattachment
-* musthavemilestoneonaccept
* password_complexity
* rememberlogin
* requirelogin
"If off, then all $terms.bugs initially have the default " _
"milestone for the product being filed in.",
- musthavemilestoneonaccept =>
- "If you are using ${field_descs.target_milestone}, do you want to require"
- _ " that the milestone be set in order for a user to set"
- _ " ${terms.abug}'s status to ${accept_status}?",
-
commentonchange_resolution => "If this option is on, the user needs to enter a short " _
"comment if the resolution of the $terms.bug changes.",
The name of a milestone is limited to [% constants.MAX_MILESTONE_SIZE FILTER html %]
characters. '[% name FILTER html %]' is too long ([% name.length %] characters).
- [% ELSIF error == "milestone_required" %]
- [% title = "Milestone Required" %]
- You must select a target milestone for [% terms.bug %]
- [%+ bug.id FILTER html %]
- if you are going to accept it. Part of accepting
- [%+ terms.abug %] is giving an estimate of when it will be fixed.
-
[% ELSIF error == "milestone_sortkey_invalid" %]
[% title = "Invalid Milestone Sortkey" %]
The sortkey '[% sortkey FILTER html %]' is not in the range