You can modify Bugzilla's status workflow to be as it used to be in previous
Bugzilla versions. There are other places in scmbug relying on particular
status names.
http://bugzillaupdate.wordpress.com/2010/07/06/bugzilla-4-0-has-a-new-default-status-workflow/

Regards,
Yavor

On Tue, Mar 8, 2011 at 02:52, Michel Pittelkow - michael-wessel.de <
[email protected]> wrote:

>  Hi,
>
> So there is actually nothing i can do but disable the is_open_state check,
> right?
>
> Thanks for your help.
>
>
>
> Mit freundlichen Grüßen / Kind regards
> Michel Pittelkow
>
> Mobil via BlackBerry
>
>  *Von*: Yavor Nikolov [mailto:[email protected]]
> *Gesendet*: Monday, March 07, 2011 11:12 PM
> *An*: Michel Pittelkow - michael-wessel.de
> *Cc*: [email protected] <[email protected]>
> *Betreff*: Re: [scmbug-users] SCMBug Commit: Error 7
>
>  Hi,
>
>  Actually list of states is dynamically retrieved from Bugzilla but
> "active" flag is hardcoded:
> $status_map->{ $status }->{ active } = 0; #Bugzilla::Bug::is_open_state(
> $status );
> ...
> $status_map->{ 'ASSIGNED' }->{ active } = 1;
> $status_map->{ 'REOPENED' }->{ active } = 1;
>
>  * I don't know why that "Bugzilla::Bug::is_open_state( $status )" has
> been disabled (maybe to prevent updating bugs in initial unassigned state).
> * If it's not possible to dynamically populate everything from Bugzilla -
> maybe it would be better to have those state names moved to config files
> instead of being hard-coded.
>
>  Regards,
> Yavor
>
> On Mon, Mar 7, 2011 at 23:44, Yavor Nikolov <[email protected]>wrote:
>
>> Hi,
>>
>> I think problem is related to fact that Bugzilla 4 has introduced new
>> default status workflow. (I haven't noticed that since I upgraded from
>> earlier version - old default workflow is preserved in such cases).
>>
>> In particular - IN_PROGRESS seems to be a new state (didn't exist in
>> earlier Bugzilla versions). To some extent Bugzilla::bug_status_map
>> implementation is hard-coded and it doesn't take into account that
>> IN_PROGRESS is an active state.
>>
>> Kind of workaround may be to try disabling open_bug_state in glue.conf
>> which will skip this validation.
>>
>> Regards,
>> Yavor
>>
>>
>> On Mon, Mar 7, 2011 at 22:48, Michel Pittelkow - michael-wessel.de <
>> [email protected]> wrote:
>>
>>> Hi there,
>>>
>>> got another Problem.
>>> Using Bugzilla 4. When I commit a test i get:
>>>
>>> ** Scmbug error 7: Bug '1' is in the 'IN_PROGRESS' state, instead of the
>>> '' or '' states.
>>>
>>> Perhaps there is a problem fetching the valud resolution states?
>>>
>>> Bugtracker.pm#392:
>>>
>>> sub valid_resolution_states_list {
>>>    my $self = shift;
>>>    my ( $bug_status, $bug_status_map ) = ( @_ );
>>>    my $list = "";
>>>    my $count = 0;
>>>
>>>    foreach my $resolution_state ( @{ $bug_status_map->{ $bug_status }->{
>>> possible_resolution_states } } ) {
>>>        $count++;
>>>        if ( $count > 1) {
>>>            $list .= " or ";
>>>        }
>>>        $list .= "'" . $resolution_state . "'";
>>>    }
>>>
>>>    if ( $count == 0 ) {
>>>        $list .= '';
>>>    } elsif ( $count == 1 ) {
>>>        $list .= " state";
>>>    } else {
>>>        $list .= " states";
>>>    }
>>>
>>>    return $list;
>>> }
>>>
>>>
>>> Mit freundlichen Grüßen / Kind regards
>>> Michel Pittelkow
>>>
>>> Via Outlook Webaccess
>>> _______________________________________________
>>> scmbug-users mailing list
>>> [email protected]
>>> http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
>>>
>>
>>
>  +----------------------------------------------------------------------+
> | - michael-wessel.de Secure E-Mail Status -                           |
> +----------------------------------------------------------------------+
> | - Die Nachricht war weder verschluesselt noch digital unterschrieben |
> +----------------------------------------------------------------------+
>
>
>
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to